From: Michael Snyder <msnyder@specifix.com>
To: Jim Blandy <jimb@codesourcery.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] Add option to skip prologue in "break FILE:LINENO" (take 2)
Date: Thu, 10 Jan 2008 21:52:00 -0000 [thread overview]
Message-ID: <1200001895.14654.33.camel@localhost.localdomain> (raw)
In-Reply-To: <m3d4s98uge.fsf@codesourcery.com>
On Thu, 2008-01-10 at 09:24 -0800, Jim Blandy wrote:
> Joel Brobecker <brobecker at adacore.com> writes:
> > Following a request for comments regarding a proposed change of behavior
> > when inserting a breakpoint on a specific line number, we received a
> > variety of comments, and it appears very clearly that the proposal
> > was at the very least controversial.
> >
> > So, here is a new proposal where the existing behavior is preserved.
> > A new set/show command is introduced to allow the user to configure
> > GDB to activate the new proposed behavior:
> >
> > (gdb) set/show breakpoint skip-prologue
> >
> > The help text for this command explains the purpose of this option:
> >
> > Set the debugger behavior when inserting a breakpoint on a specific line.
> > When inserting a breakpoint on a specific line number that corresponds
> > to the prologue of a function, the debugger will automatically adjust
> > its location to the first line past the prologue if this option is set.
> >
> > By default, this option is OFF, preserving the current behavior.
> > I think this should take care of all the objections I read so far.
>
> Some of Michael's objections I didn't understand at all --- he seemed
> to believe that the change would affect GDB's behavior in ways I think
> it won't. I don't think your change would affect the usage that was
> most important to him.
>
> I'd like to get that (or perhaps just me) straightened out before we
> add an option. Options of this sort are effective at resolving
> contentious mailing list threads, but not very effective for the vast
> majority of users. Most users have little or no interest in GDB for
> its own sake, and won't look for options like 'set breakpoint
> skip-prologue', so subtle improvements that are disabled by default
> have almost no impact.
You're right -- initializations are treated as part of the function
body, not the prologue. My concerns were largely unfounded. ;-)
next prev parent reply other threads:[~2008-01-10 21:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 15:13 Joel Brobecker
2008-01-10 17:25 ` Jim Blandy
2008-01-10 21:52 ` Michael Snyder [this message]
2008-01-10 22:15 ` Jim Blandy
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=1200001895.14654.33.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.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