public inbox for
 help / color / mirror / Atom feed
From: Andrew Cagney <>
To: frysk <>
Subject: back-traces back to normal
Date: Sat, 21 Jun 2008 14:14:00 -0000	[thread overview]
Message-ID: <> (raw)


I've been fixing a number of symbol related problems that can be seen 
when doing backtraces, for instance:

On F-9:
  $ ./frysk/bindir/fstack $$
  Task #18929
  #0 0x000000310d49a835 in __waitpid() from
  #1 0x0000000000435a51 in [unknown] from bash
  #2 0x000000000043786e in wait_for() from bash
frame #1 is now correctly reporting [unknown], an elfutils regression 
was causing _start to be printed.

and on F-8:
  $ ./frysk/bindir/fstack $$
  Task #11813
  #0 0x00110416 in __kernel_vsyscall() from [vdso]
  #1 0x0807d210 in wait_for() from bash
frame #1 has [vdso] and the symbol appearing again, a fix while 
converting cni to jni caused this

I've added/enabled tests to check for both of these cases.


                 reply	other threads:[~2008-06-20 13:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

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