From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb@sources.redhat.com, Markus.Kremer@tenovis.com
Subject: Re: wrong backtrace / __JCR_LIST__ instead of real function name
Date: Tue, 21 Oct 2003 14:21:00 -0000 [thread overview]
Message-ID: <200310211420.h9LEKwIO018541@duracef.shout.net> (raw)
Hello,
Try gdb 6.0, which has improved backtracing in system calls.
Michael C
GDB QA Guy
next reply other threads:[~2003-10-21 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 14:21 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-21 11:05 Kremer Markus (MPI/SFR)
2003-10-21 12:54 ` Daniel Jacobowitz
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=200310211420.h9LEKwIO018541@duracef.shout.net \
--to=mec@shout.net \
--cc=Markus.Kremer@tenovis.com \
--cc=gdb@sources.redhat.com \
/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).