https://bugs.kde.org/show_bug.cgi?id=469783
--- Comment #2 from Vitaly Chikunov <v...@altlinux.org> --- This is still true for valgrind-3.22.0: ``` builder@armv7l:~/RPM/BUILD/valgrind-3.22.0$ ./vg-in-place /bin/true ==228878== Memcheck, a memory error detector ==228878== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==228878== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info ==228878== Command: /bin/true ==228878== ==228878== Invalid write of size 4 ==228878== at 0x10568: ??? (in /bin/true) ==228878== by 0xFEC454E3: ??? ==228878== Address 0xfec454b4 is on thread 1's stack ==228878== 24 bytes below stack pointer ==228878== ==228878== Invalid write of size 4 ==228878== at 0x18D72: ??? (in /bin/true) ==228878== Address 0xfec453d4 is on thread 1's stack ==228878== 224 bytes below stack pointer ==228878== ==228878== Invalid write of size 4 ==228878== at 0x1876A: ??? (in /bin/true) ==228878== Address 0xfec45434 is on thread 1's stack ==228878== 104 bytes below stack pointer ==228878== ==228878== Invalid write of size 4 ==228878== at 0x107F0: ??? (in /bin/true) ==228878== Address 0xfec4545c is on thread 1's stack ==228878== 64 bytes below stack pointer ==228878== ==228878== Invalid write of size 4 ==228878== at 0x17FDE: ??? (in /bin/true) ==228878== Address 0xfec45458 is on thread 1's stack ==228878== 24 bytes below stack pointer ==228878== ==228878== Invalid write of size 4 ==228878== at 0x18D0E: ??? (in /bin/true) ==228878== Address 0xfec45460 is on thread 1's stack ==228878== 16 bytes below stack pointer ==228878== ==228878== Invalid write of size 4 ==228878== at 0x1854E: ??? (in /bin/true) ==228878== Address 0xfec45458 is on thread 1's stack ==228878== 24 bytes below stack pointer ==228878== ==228878== Syscall param set_robust_list(head) points to uninitialised byte(s) ==228878== at 0x10A16: ??? (in /bin/true) ==228878== by 0x185B1: ??? (in /bin/true) ==228878== Address 0x4000074 is in the brk data segment 0x4000000-0x4000873 ==228878== ==228878== Invalid write of size 4 ==228878== at 0x19652: ??? (in /bin/true) ==228878== Address 0xfec45490 is on thread 1's stack ==228878== 32 bytes below stack pointer ==228878== ==228878== Invalid write of size 4 ==228878== at 0x21ADE: ??? (in /bin/true) ==228878== Address 0xfec45488 is on thread 1's stack ==228878== 16 bytes below stack pointer ==228878== ==228878== Invalid write of size 4 ==228878== at 0x19722: ??? (in /bin/true) ==228878== Address 0xfec454a0 is on thread 1's stack ==228878== 16 bytes below stack pointer ==228878== ==228878== Invalid write of size 4 ==228878== at 0x18EA0: ??? (in /bin/true) ==228878== Address 0xfec4543c is on thread 1's stack ==228878== 80 bytes below stack pointer ==228878== ==228878== Invalid write of size 4 ==228878== at 0x2991A: ??? (in /bin/true) ==228878== Address 0xfec44450 is not stack'd, malloc'd or (recently) free'd ==228878== ==228878== ==228878== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==228878== Access not within mapped region at address 0xFEC44450 ==228878== at 0x2991A: ??? (in /bin/true) ==228878== If you believe this happened as a result of a stack ==228878== overflow in your program's main thread (unlikely but ==228878== possible), you can try to increase the size of the ==228878== main thread stack using the --main-stacksize= flag. ==228878== The main thread stack size used in this run was 8388608. ==228878== ==228878== HEAP SUMMARY: ==228878== in use at exit: 0 bytes in 0 blocks ==228878== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==228878== ==228878== All heap blocks were freed -- no leaks are possible ==228878== ==228878== Use --track-origins=yes to see where uninitialised values come from ==228878== For lists of detected and suppressed errors, rerun with: -s ==228878== ERROR SUMMARY: 13 errors from 13 contexts (suppressed: 0 from 0) Segmentation fault ``` -- You are receiving this mail because: You are watching all bug changes.
