From: Eli Zaretskii <eliz@gnu.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: jason-swarelist@molenda.com, gdb-patches@sources.redhat.com
Subject: Re: The gdb x86 function prologue parser
Date: Sun, 12 Jun 2005 08:44:00 -0000 [thread overview]
Message-ID: <ull5g6k2g.fsf@gnu.org> (raw)
In-Reply-To: <200506120748.j5C7m75C011986@elgar.sibelius.xs4all.nl> (message from Mark Kettenis on Sun, 12 Jun 2005 09:48:07 +0200 (CEST))
> Date: Sun, 12 Jun 2005 09:48:07 +0200 (CEST)
> From: Mark Kettenis <mark.kettenis@xs4all.nl>
> CC: gdb-patches@sources.redhat.com
>
> 1. Finding out the gory details about the stack frame being executed.
>
> 2. Determining the first bit of code after the prologue, i.e. the
> first bit of real code.
>
> For (2) following jumps is usually a very bad thing to do.
>
> That said, I'm not sure this dual usage of the prologue scanner really
> makes sense these days. There is a certain lack of consistency in gdb
> how we handle this anyway. Maybe the best thing to do is to not use
> the prologue scanner for 2 at all.
In what situations would GDB need to use (2), and what are the
alternative(s)?
next prev parent reply other threads:[~2005-06-12 8:44 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 [this message]
[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
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=ull5g6k2g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jason-swarelist@molenda.com \
--cc=mark.kettenis@xs4all.nl \
/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