From: Michael Snyder <msnyder@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Klee Dienes <klee@mit.edu>, gdb-patches@sources.redhat.com
Subject: Re: The gdb x86 function prologue parser
Date: Mon, 13 Jun 2005 18:21:00 -0000 [thread overview]
Message-ID: <42ADCE94.1090804@redhat.com> (raw)
In-Reply-To: <uaclv7lzh.fsf@gnu.org>
Eli Zaretskii wrote:
>>Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, jason-swarelist@molenda.com,
>> gdb-patches@sources.redhat.com
>>From: Klee Dienes <klee@mit.edu>
>>Date: Sun, 12 Jun 2005 07:59:01 -0400
>>
>>(2) gets used by GDB when it wants to know where to set a breakpoint
>>(the idea being that when you say "break foo", it wants to insert the
>>breakpoint in foo() after the prologue has been fully executed).
>>
>>It also gets used where GDB wants to know if it is inside a function
>>prologue for some reason (for example, so "next" knows if it has
>>stepped into a new function, or simply jumped interprocedurally).
>
>
> Thanks.
>
> (I'm collecting info for gdbint.texinfo, that's why I asked.)
Also so "step into" can step past the prologue and not stop
until it has reached user code. Same basic purpose as 2),
but different context.
next prev parent reply other threads:[~2005-06-13 18:21 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 [this message]
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=42ADCE94.1090804@redhat.com \
--to=msnyder@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=klee@mit.edu \
/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