https://bugs.kde.org/show_bug.cgi?id=492947
Paul Floyd <pjfl...@wanadoo.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pjfl...@wanadoo.fr
--- Comment #1 from Paul Floyd <pjfl...@wanadoo.fr> ---
(In reply to Fred M from comment #0)
> Would it be a build option to make valgrind / massif / backtraces robust to
> the strip ?
No. Simply don't use strip. From README_PACKAGERS:
-- Don't strip the debug info off lib/valgrind/$platform/vgpreload*.so
in the installation tree. Either Valgrind won't work at all, or it
will still work if you do, but will generate less helpful error
messages. Here's an example:
The example in the README is a bit out of date. This issue looks like another
case where it is a problem.
The worst thing about stripped binaries for us (Valgrind developers) is that
bug reports won't have useful stack traces.
--
You are receiving this mail because:
You are watching all bug changes.
