From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: jimb@red-bean.com, brobecker@adacore.com,
gdb-patches@sources.redhat.com
Subject: Re: [RFC/RFA/i386] pb reading insns if breakpoints still inserted
Date: Fri, 28 Apr 2006 21:13:00 -0000 [thread overview]
Message-ID: <20060428211258.GA6713@nevyn.them.org> (raw)
In-Reply-To: <200604282109.k3SL9Jwp020317@elgar.sibelius.xs4all.nl>
On Fri, Apr 28, 2006 at 11:09:19PM +0200, Mark Kettenis wrote:
> But if we don't have debug information, what's the point in trying to
> skip the prologue in order to put a breakpoint on ... eh what exactly?
> Isn't it better to just punt prologue skipping in that case and place
> the breakpoint on the first instruction of the code?
Yes, I agree.
I'd like to note, though, that the way we skip prologues based on debug
information is completely wrong. It only works with GCC and with other
compilers that have chosen to be bug-compatible with GCC. DWARF does
support a "this is the end of the prologue" flag, but I don't know if
GCC emits it, and I'm pretty positive GDB doesn't know how to consume
it.
[GCC just emits a line note before and after the prologue - even if
they're on the same line.]
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-28 21:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 17:12 Joel Brobecker
2006-04-28 17:54 ` Jim Blandy
2006-04-28 18:40 ` Mark Kettenis
2006-04-28 18:48 ` Joel Brobecker
2006-04-28 20:58 ` Jim Blandy
2006-04-28 21:09 ` Mark Kettenis
2006-04-28 21:13 ` Daniel Jacobowitz [this message]
2006-04-28 21:42 ` Jim Blandy
2006-04-28 21:54 ` Joel Brobecker
2006-04-28 21:49 ` Joel Brobecker
2006-04-28 22:00 ` Jim Blandy
2006-04-29 14:20 ` Eli Zaretskii
2006-04-29 14:28 ` Daniel Jacobowitz
2006-04-29 14:51 ` Eli Zaretskii
2006-04-29 15:06 ` Daniel Jacobowitz
2006-04-29 16:57 ` Eli Zaretskii
2006-04-29 23:14 ` Daniel Jacobowitz
2006-05-01 16:36 ` Mark Kettenis
2006-05-01 17:06 ` Joel Brobecker
2006-05-05 18:16 ` 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=20060428211258.GA6713@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@red-bean.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