https://bugs.kde.org/show_bug.cgi?id=445032
--- Comment #6 from Paul Floyd <pjfl...@wanadoo.fr> --- paulf@freebsd:~/scratch/sigreturn $ valgrind ./pthread_sigreturn_clang ==866== Memcheck, a memory error detector ==866== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==866== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info ==866== Command: ./pthread_sigreturn_clang ==866== ==866== Invalid read of size 4 ==866== at 0x720526B: ??? (in /lib/libthr.so.3) ==866== by 0x72048BD: ??? (in /lib/libthr.so.3) ==866== by 0x381A64F3: ??? (in /usr/local/libexec/valgrind/memcheck-x86-freebsd) ==866== by 0x72B973E: sleep (in /lib/libc.so.7) ==866== by 0x4018F2: main (in /usr/home/paulf/scratch/sigreturn/pthread_sigreturn_clang) ==866== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==866== ==866== ==866== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==866== Access not within mapped region at address 0x0 ==866== at 0x720526B: ??? (in /lib/libthr.so.3) ==866== by 0x72048BD: ??? (in /lib/libthr.so.3) ==866== by 0x381A64F3: ??? (in /usr/local/libexec/valgrind/memcheck-x86-freebsd) ==866== by 0x72B973E: sleep (in /lib/libc.so.7) ==866== by 0x4018F2: main (in /usr/home/paulf/scratch/sigreturn/pthread_sigreturn_clang) ==866== If you believe this happened as a result of a stack ==866== overflow in your program's main thread (unlikely but ==866== possible), you can try to increase the size of the ==866== main thread stack using the --main-stacksize= flag. ==866== The main thread stack size used in this run was 16777216. To get this I changed the ASLR sysctls paulf@freebsd:~/scratch/sigreturn $ sysctl -a | grep -i aslr kern.elf32.aslr.stack_gap: 0 (default is 3) kern.elf32.aslr.honor_sbrk: 1 kern.elf32.aslr.pie_enable: 1 (default is 0) kern.elf32.aslr.enable: 1 (default is 0) vm.aslr_restarts: 0 Are yoiu using ASLR as above? -- You are receiving this mail because: You are watching all bug changes.
