public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "rjgebis at hotmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/12679] New: gdb does show user code when no libc available
Date: Fri, 15 Apr 2011 17:40:00 -0000	[thread overview]
Message-ID: <bug-12679-4717@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=12679

           Summary: gdb does show user code when no libc available
           Product: gdb
           Version: 7.2
            Status: NEW
          Severity: minor
          Priority: P2
         Component: c++
        AssignedTo: unassigned@sourceware.org
        ReportedBy: rjgebis@hotmail.com


I just installed from source 7.2 gdb release on CentOS 5.6.
After loading core file switching between threads when I do list to show source
I get source from last list where user code was available.

For example I am on thread 5 and do "where"
it shows stack with libc on top of the stack. If I do up few times until I get
to frame where user code executed, I do "list" and see my code.

Now I switch to some other thread and right away I issue "list", if libc is at
top of the stack 
list shows wrong source from user stack (looks like last "list" from different
thread - user code)
instead of printing "No source available" until i go up the stack to user code.

-- 
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.


             reply	other threads:[~2011-04-15 17:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-15 17:40 rjgebis at hotmail dot com [this message]
2011-04-15 17:40 ` [Bug corefiles/12679] " rjgebis at hotmail 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-12679-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: link
Be 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).