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

> From: Pedro Alves <pedro@codesourcery.com>
> Date: Tue, 12 Aug 2008 00:34:24 +0100
> 
> So, this patch changes the "set breakpoints always-inserted" setting to
> be a three-state.  on and off, the same as before, and a new mode,
> "follow-non-stop".

How about calling this state "auto"?

> 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.

> +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}".

Also, it would be helpful to have an index entry here, something like

  @cindex non-stop mode, and @code{breakpoint always-inserted}


  parent reply	other threads:[~2008-08-12 18:18 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 [this message]
2008-08-12 20:07   ` Pedro Alves
2008-08-12 20:12     ` Daniel Jacobowitz
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=ur68ugksf.fsf@gnu.org \
    --to=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