https://bugs.kde.org/show_bug.cgi?id=469783
--- Comment #4 from Vitaly Chikunov <v...@altlinux.org> --- It's still crashes with tool none: ``` builder@armv7l:~/RPM/BUILD/valgrind-3.22.0$ ./vg-in-place --tool=none /bin/true ==1347567== Nulgrind, the minimal Valgrind tool ==1347567== Copyright (C) 2002-2017, and GNU GPL'd, by Nicholas Nethercote. ==1347567== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info ==1347567== Command: /bin/true ==1347567== ==1347567== ==1347567== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==1347567== Access not within mapped region at address 0xFEF1C4A0 ==1347567== at 0x2991A: ??? (in /bin/true) ==1347567== If you believe this happened as a result of a stack ==1347567== overflow in your program's main thread (unlikely but ==1347567== possible), you can try to increase the size of the ==1347567== main thread stack using the --main-stacksize= flag. ==1347567== The main thread stack size used in this run was 8388608. ==1347567== Segmentation fault ``` With suppressor from Debian: ``` builder@armv7l:~/RPM/BUILD/valgrind-3.22.0$ ./vg-in-place --suppressions=armhf-stackclash.supp /bin/true ==1355694== Memcheck, a memory error detector ==1355694== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==1355694== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info ==1355694== Command: /bin/true ==1355694== ==1355694== Syscall param set_robust_list(head) points to uninitialised byte(s) ==1355694== at 0x10A16: ??? (in /bin/true) ==1355694== by 0x185B1: ??? (in /bin/true) ==1355694== Address 0x4000074 is in the brk data segment 0x4000000-0x4000873 ==1355694== ==1355694== ==1355694== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==1355694== Access not within mapped region at address 0xFEF00450 ==1355694== at 0x2991A: ??? (in /bin/true) ==1355694== If you believe this happened as a result of a stack ==1355694== overflow in your program's main thread (unlikely but ==1355694== possible), you can try to increase the size of the ==1355694== main thread stack using the --main-stacksize= flag. ==1355694== The main thread stack size used in this run was 8388608. ==1355694== ==1355694== HEAP SUMMARY: ==1355694== in use at exit: 0 bytes in 0 blocks ==1355694== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==1355694== ==1355694== All heap blocks were freed -- no leaks are possible ==1355694== ==1355694== Use --track-origins=yes to see where uninitialised values come from ==1355694== For lists of detected and suppressed errors, rerun with: -s ==1355694== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 12 from 12) Segmentation fault builder@armv7l:~/RPM/BUILD/valgrind-3.22.0$ cat armhf-stackclash.supp # On armhf, stack-clash-protector is implemented by writing out of stack # bounds. https://bugzilla.redhat.com/show_bug.cgi?id=1522678 { stack-clash-protection-armhf Memcheck:Addr4 obj:* } ``` -- You are receiving this mail because: You are watching all bug changes.
