public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/14846] New: traceframes and shared libraries Date: Thu, 15 Nov 2012 14:53:00 -0000 [thread overview] Message-ID: <bug-14846-4717@http.sourceware.org/bugzilla/> (raw) 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.
next reply other threads:[~2012-11-15 14:53 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-15 14:53 palves at redhat dot com [this message] 2012-11-15 14:56 ` [Bug gdb/14846] " palves at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-14846-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).