Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: Add a third mode to "breakpoints always-inserted", and make it 	the default
Date: Tue, 12 Aug 2008 20:12:00 -0000	[thread overview]
Message-ID: <20080812201133.GA25501@caradoc.them.org> (raw)
In-Reply-To: <200808122107.20295.pedro@codesourcery.com>

On Tue, Aug 12, 2008 at 09:07:19PM +0100, Pedro Alves wrote:
> > How about calling this state "auto"?
> 
> I like it.

Me, too.
> 
> > > In the latter mode, GDB will behave as "on", if
> > > we're in non-stop mode, and as "off" if we're in all-stop mode.
> >
> > I think _behave_ as "on" is not a good idea.  I suggest that it
> > actually _set_ the option "on".  That way, code elsewhere will need
> > only to look at a single option, and won't need to know that if the
> > value is follow-non-stop, it needs to check another flag.
> 
> All the common code already goes through this predicate:
> 
>  +int
>  +breakpoints_always_inserted_mode (void)
>  +{
>  +  return (always_inserted_mode == always_inserted_on
>  +         || (always_inserted_mode == always_inserted_follow_non_stop
>  +             && non_stop));
>  +}
>  -int breakpoints_always_inserted_mode (void)
>  -{
>  -  return always_inserted_mode;
>  -}
>  -
> 
> Note that I didn't have to touch any of infrun.c, or breakpoint
> management functions in breakpoint.c, where the predicate is checked.
> 
> If I kept it as an boolean, I'd have to instead change the "set non-stop"
> command implementation, which means I'd have to export a setter for the
> internal breakpoint.c variable.  Either way, one setting has to know
> about the other.  This way seemed more centralised.
> 
> In any case, I can't seem to come up with a sentence that
> describes the auto behaviour without using "behaves as".  If you can
> suggest any, I'd appreciate it.
> 
> > > +This is the default mode.  If gdb is controlling the inferior in
> > > +non-stop mode (@pxref{Non-Stop Mode}), gdb behaves as if
> > > +always-inserted mode is on.  If gdb is controlling the inferior in
> > > +all-stop mode, gdb behaves as if always-inserted mode is off.
> >
> > We don't use a literal "gdb" in the manual, we use "@value{GDBN}".
> 
> Ooops.  Fixed.
> 
> >
> > Also, it would be helpful to have an index entry here, something like
> >
> >   @cindex non-stop mode, and @code{breakpoint always-inserted}
> 
> Done, and done, I think.

No, you added:

> +@cindex non-stop mode

I'm sure that one doesn't go here :-)

> +  if (always_inserted_mode == always_inserted_auto)
> +    fprintf_filtered (file,
> +		      _("Always inserted breakpoint mode is %s (currently %s).\n"),
> +		      value, non_stop ? "on" : "off");

I suggest calling breakpoints_always_inserted_mode here instead of
checking non_stop.

Otherwise, the code looks fine - though I'd like to reach an agreement
with Vladimir about set non-stop first.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-08-12 20:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-11 23:34 Pedro Alves
2008-08-12  1:52 ` Pedro Alves
2008-08-12  6:23 ` Vladimir Prus
2008-08-12 18:18 ` Eli Zaretskii
2008-08-12 20:07   ` Pedro Alves
2008-08-12 20:12     ` Daniel Jacobowitz [this message]
2008-08-12 20:37       ` Pedro Alves
2008-08-12 20:41         ` Daniel Jacobowitz
2008-08-12 21:45           ` Pedro Alves
2008-08-12 23:06             ` Daniel Jacobowitz
2008-08-13  3:19               ` Eli Zaretskii
2008-08-13 14:01       ` Pedro Alves

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=20080812201133.GA25501@caradoc.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@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