oh, this one looks tricky!

May be adding " -fstack-protector-strong" or  -fstack-protector-all" to normal build CFLAGS will uncover it on other distros?


But debugging even in simple case looks .... time consuming:

https://wiki.gentoo.org/wiki/Stack_smashing_debugging_guide

пн, 1 мая 2023 г., 00:35 Stefan de Konink <stefan@konink.de>:
[Thread 0x7ffb70db66c0 (LWP 715673) exited]
*** stack smashing detected ***: terminated

Thread 653 "cin" received signal SIGABRT, Aborted.
[Switching to Thread 0x7ffb6bfff6c0 (LWP 715674)]
__pthread_kill_implementation (threadid=<optimized out>,
signo=signo@entry=6,
    no_tid=no_tid@entry=0) at pthread_kill.c:44
Downloading source file /usr/src/debug/glibc/glibc/nptl/pthread_kill.c
44            return INTERNAL_SYSCALL_ERROR_P (ret) ?
INTERNAL_SYSCALL_ERRNO (ret) : 0;
(gdb) bt
#0  __pthread_kill_implementation (threadid=<optimized out>,
    signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1  0x00007ffff5fa7953 in __pthread_kill_internal (signo=6,
    threadid=<optimized out>) at pthread_kill.c:78
#2  0x00007ffff5f58ea8 in __GI_raise (sig=sig@entry=6)
    at ../sysdeps/posix/raise.c:26
#3  0x00007ffff5f4253d in __GI_abort () at abort.c:79
#4  0x00007ffff5f4329e in __libc_message (
    fmt=fmt@entry=0x7ffff60ba535 "*** %s ***: terminated\n")
    at ../sysdeps/posix/libc_fatal.c:150
#5  0x00007ffff6037c5b in __GI___fortify_fail (
    msg=msg@entry=0x7ffff60ba51d "stack smashing detected")
    at fortify_fail.c:24
#6  0x00007ffff6037c36 in __stack_chk_fail () at stack_chk_fail.c:24
#7  0x00005555560a42bd in BC_WindowEvents::run (this=<optimized out>)
    at bcwindowevents.C:138
#8  0x00005555560aca95 in Thread::entrypoint (parameters=0x7fff38554740)
    at thread.C:70
#9  0x00007ffff5fa5bb5 in start_thread (arg=<optimized out>)
    at pthread_create.c:444
#10 0x00007ffff6027d90 in clone3 ()
    at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
(gdb)

--
Stefan