Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Add option to skip prologue in "break FILE:LINENO" (take 2)
Date: Thu, 10 Jan 2008 17:25:00 -0000	[thread overview]
Message-ID: <m3d4s98uge.fsf@codesourcery.com> (raw)
In-Reply-To: <20080110151312.GC13181@adacore.com> (Joel Brobecker's message of "Thu, 10 Jan 2008 07:13:12 -0800")


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.


  reply	other threads:[~2008-01-10 17:25 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 [this message]
2008-01-10 21:52   ` Michael Snyder
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=m3d4s98uge.fsf@codesourcery.com \
    --to=jimb@codesourcery.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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