https://bugs.kde.org/show_bug.cgi?id=509666
--- Comment #4 from Marc-Oliver Straub <marc-oliver.str...@advantest.com> --- Interesting: I enabled -g for the gperftools compile (to get your line numbers), the valgrind output now changed: ==256708== Memcheck, a memory error detector ==256708== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al. ==256708== Using Valgrind-3.24.0 and LibVEX; rerun with -h for copyright info ==256708== Command: ./starter ==256708== ==256708== Stack overflow in thread #1: can't grow stack to 0x1ffe601000 ==256708== ==256708== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==256708== Access not within mapped region at address 0x1FFE601FF8 ==256708== Stack overflow in thread #1: can't grow stack to 0x1ffe601000 ==256708== at 0x484482F: malloc (vg_replace_malloc.c:446) ==256708== If you believe this happened as a result of a stack ==256708== overflow in your program's main thread (unlikely but ==256708== possible), you can try to increase the size of the ==256708== main thread stack using the --main-stacksize= flag. ==256708== The main thread stack size used in this run was 10485760. After increasing the stack size, it now hangs again (or, is in a infinite recursion). Ctrl-C now prints: ==260595== Process terminating with default action of signal 2 (SIGINT) ==260595== at 0x527A280: free (in /opt/hp93000rt/el9/x86_64/gperftools_2.16/lib/libtcmalloc_minimal.so.4.6.0) ==260595== by 0x528FC3B: MallocExtension::instance() (in /opt/hp93000rt/el9/x86_64/gperftools_2.16/lib/libtcmalloc_minimal.so.4.6.0) ==260595== by 0x528FC40: MallocExtension::instance() (in /opt/hp93000rt/el9/x86_64/gperftools_2.16/lib/libtcmalloc_minimal.so.4.6.0) ==260595== by 0x528FC40: MallocExtension::instance() (in /opt/hp93000rt/el9/x86_64/gperftools_2.16/lib/libtcmalloc_minimal.so.4.6.0) ==260595== by 0x528FC40: MallocExtension::instance() (in /opt/hp93000rt/el9/x86_64/gperftools_2.16/lib/libtcmalloc_minimal.so.4.6.0) ==260595== by 0x528FC40: MallocExtension::instance() (in /opt/hp93000rt/el9/x86_64/gperftools_2.16/lib/libtcmalloc_minimal.so.4.6.0) ==260595== by 0x528FC40: MallocExtension::instance() (in /opt/hp93000rt/el9/x86_64/gperftools_2.16/lib/libtcmalloc_minimal.so.4.6.0) ==260595== by 0x528FC40: MallocExtension::instance() (in /opt/hp93000rt/el9/x86_64/gperftools_2.16/lib/libtcmalloc_minimal.so.4.6.0) ==260595== by 0x528FC40: MallocExtension::instance() (in /opt/hp93000rt/el9/x86_64/gperftools_2.16/lib/libtcmalloc_minimal.so.4.6.0) ==260595== by 0x528FC40: MallocExtension::instance() (in /opt/hp93000rt/el9/x86_64/gperftools_2.16/lib/libtcmalloc_minimal.so.4.6.0) ==260595== by 0x528FC40: MallocExtension::instance() (in /opt/hp93000rt/el9/x86_64/gperftools_2.16/lib/libtcmalloc_minimal.so.4.6.0) ==260595== by 0x528FC40: MallocExtension::instance() (in /opt/hp93000rt/el9/x86_64/gperftools_2.16/lib/libtcmalloc_minimal.so.4.6.0) But still no line numbers... The valgrind provided by RedHat doesn't have debug symbols, pstack is unusable. -- You are receiving this mail because: You are watching all bug changes.
