From: Eli Zaretskii <eliz@gnu.org>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: The gdb x86 function prologue parser
Date: Fri, 10 Jun 2005 21:18:00 -0000 [thread overview]
Message-ID: <ud5qt9ahd.fsf@gnu.org> (raw)
In-Reply-To: <42A9F7F6.5050602@redhat.com> (message from Michael Snyder on Fri, 10 Jun 2005 13:28:38 -0700)
> Date: Fri, 10 Jun 2005 13:28:38 -0700
> From: Michael Snyder <msnyder@redhat.com>
> CC: Jason Molenda <jmolenda@apple.com>, gdb-patches@sources.redhat.com,
> kettenis@jive.nl
>
> Prologue parsing is a black art, on its way to becoming a
> lost art thanks to our increasing dependance on dwarf cfi.
There are still quite a few platforms that cannot rely on CFI. Not to
mention that currently there are many situations where I can't get a
decent backtrace even with DWARF CFI.
> It would be great if Jason could preserve some of what he's
> having to relearn/reinvent -- but it wouldn't be fair of us
> to require this of him.
I didn't require, I said I'd appreciate if he did that.
Someone must remind people from time to time to try documenting the
internals. Otherwise gdbint.texinfo will never get better.
next prev parent reply other threads:[~2005-06-10 21:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 5:51 Jason Molenda
2005-06-08 13:24 ` Daniel Jacobowitz
2005-06-08 16:58 ` Jason Molenda
2005-06-12 7:48 ` Mark Kettenis
2005-06-12 8:44 ` Eli Zaretskii
[not found] ` <3364FC4D-63FB-493B-9136-D118F74C13BB@mit.edu>
2005-06-12 13:17 ` Eli Zaretskii
2005-06-12 14:28 ` Daniel Jacobowitz
2005-06-13 18:21 ` Michael Snyder
2005-06-13 19:13 ` Eli Zaretskii
2005-06-08 14:52 ` Eli Zaretskii
2005-06-08 17:01 ` Jason Molenda
2005-06-08 18:03 ` Eli Zaretskii
2005-06-08 19:58 ` Andreas Schwab
2005-06-09 6:26 ` Jason Molenda
2005-06-09 9:02 ` Andreas Schwab
2005-06-10 20:23 ` Michael Snyder
2005-06-12 7:57 ` Mark Kettenis
2005-06-10 20:29 ` Michael Snyder
2005-06-10 21:18 ` Eli Zaretskii [this message]
2005-06-12 7:07 ` Mark Kettenis
2005-06-12 8:50 ` Eli Zaretskii
2005-06-13 22:04 ` Jason Molenda
2005-06-13 22:35 ` Mark Kettenis
2005-06-13 22:51 ` 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=ud5qt9ahd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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