[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [valgrind] [Bug 79362] Debug info is lost for .so files when they are dlclose'd
From:       Ivo Raisr <bugzilla_noreply () kde ! org>
Date:       2017-08-01 13:04:03
Message-ID: bug-79362-17878-YplIwl9o8U () http ! bugs ! kde ! org/
[Download RAW message or body]

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

--- Comment #69 from Ivo Raisr <ivosh@ivosh.net> ---
Just a quick note:
Once this functionality is integrated, remove the corresponding entry from www
page http://valgrind.org/help/projects.html:

-----------------------
Preserving debugging information
Currently, Valgrind unloads debugging information for shared objects when they
are unloaded with dlclose(). If the shared object has a memory leak, the stack
trace for Memcheck's error message at termination will be missing entries,
which makes fixing the leak difficult. This is described in bug report #79362.

One way to fix this would be to change things so that Valgrind records
source-level information for stack traces, rather than code addresses. It is
not entirely clear how to do this in a way that avoids unnecessary debug
information lookups, and nor how to avoid increasing the amount of memory used.
An implementation would help clarify the problem and show if this approach is
feasible. This project is of intermediate difficulty. (Added August 27, 2005)
-----------------------

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]