From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-prs-return-12639-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Received: (qmail 16441 invoked by alias); 15 Nov 2012 14:53:42 -0000
Received: (qmail 16419 invoked by uid 48); 15 Nov 2012 14:53:41 -0000
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: gdb
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: palves at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-14846-4717@http.sourceware.org/bugzilla/>
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
X-SW-Source: 2012-q4/txt/msg00249.txt.bz2

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.