From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb@sources.redhat.com
Subject: fixing 'backtrace through sleep' on the cheap
Date: Mon, 04 Aug 2003 23:40:00 -0000 [thread overview]
Message-ID: <200308042340.h74Ne3XD010039@duracef.shout.net> (raw)
In a nutshell, the problem is that gdb 6.0 does a lot worse than
gdb 5.3 when it's backtracing through functions with no debug info
and a failed prologue analysis.
I'm about to write a patch for the i386 prologue analyzer so that it
recognizes a few more instructions that are turning up in common
prologues, particularly the code for 'sleep' in glibc 2.2.93-5-rh.
I don't know whether such a patch has any chance of approval.
I'm hoping this message will flush out any disapproval
before the patch plops onto the mailing list.
Elena Z suggested this earlier today, and I think it's the best way
forward since we have a gdb 6.0 release coming shortly.
For gdb 6.1 I agree with Daniel J's suggestion to use the 'abstract
interpretation' machinery in s390-tdep.c.
Michael C
reply other threads:[~2003-08-04 23:40 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:
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=200308042340.h74Ne3XD010039@duracef.shout.net \
--to=mec@shout.net \
--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).