[valgrind] [Bug 390765] Stack traces given by Memcheck aren't helpful

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=390765

sara...@163.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #2 from sara...@163.com ---
Thanks for the response, my libc.so.0 is stripped, I replaced it with
unstripped one and now valgrind works fine.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 390765] Stack traces given by Memcheck aren't helpful

[Tom Hughes]

https://bugs.kde.org/show_bug.cgi?id=390765

Tom Hughes  changed:

   What|Removed |Added

 CC||t...@compton.nu

--- Comment #1 from Tom Hughes  ---
Compiling your program with -fno-omit-frame-pointer doesn't help if the problem
occurs in libc and libc has been compiled without any way to unwind the stack.

Almost certainly your libc does not have DWARF frame unwind information
available and has been compiled without frame pointers (completely normal these
days).

If your distro has debug packages then installing the debug package for libc
may well help.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 390765] Stack traces given by Memcheck aren't helpful

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=390765

sara...@163.com changed:

   What|Removed |Added

 CC||sara...@163.com

-- 
You are receiving this mail because:
You are watching all bug changes.