This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/14846] New: traceframes and shared libraries
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 15 Nov 2012 14:53:40 +0000
- Subject: [Bug gdb/14846] New: traceframes and shared libraries
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=14846
Bug #: 14846
Summary: traceframes and shared libraries
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
AssignedTo: unassigned@sourceware.org
ReportedBy: palves@redhat.com
Classification: Unclassified
Tracepoints and dynamic loading/unloading of shared libraries just don't mix up
well today. Consider e.g., your program dlopens a library, and you set a
tracepoint somewhere in the DSO. Then you tstart, and let the program
continue. The tracepoint it hit, and before you tstop, the program dlcloses
the library. You now tstop, and tfind to inspect the tracepoint hit, but that
will be broken, because the library is no longer loaded.
Inspecting traceframes in a sense is like inspecting a core dump. But with
traceframes, GDB doesn't have the complete picture of the state of the shared
libraries at the time the tracepoint was collected.
On GNU/Linux, it may be possible to collect enough of the dynamic linker
structures manually so that GDB can reconstruct the DSO list from a traceframe
back to what it was when the tracepoint was hit.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.