From: Pedro Alves <pedro@codesourcery.com>
To: Daniel Jacobowitz <drow@false.org>
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:37:00 -0000 [thread overview]
Message-ID: <200808122137.00425.pedro@codesourcery.com> (raw)
In-Reply-To: <20080812201133.GA25501@caradoc.them.org>
On Tuesday 12 August 2008 21:11:33, Daniel Jacobowitz wrote:
> On Tue, Aug 12, 2008 at 09:07:19PM +0100, Pedro Alves wrote:
> > > 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 :-)
>
Where does it go then? I generated html, and I see two "non-stop mode"
index entries, one of them points here, to the auto option, the other
points to the "set non-stop mode" option.
> > + 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.
Sure.
>
> Otherwise, the code looks fine - though I'd like to reach an agreement
> with Vladimir about set non-stop first.
Certainly.
--
Pedro Alves
next prev parent reply other threads:[~2008-08-12 20:37 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
2008-08-12 20:37 ` Pedro Alves [this message]
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=200808122137.00425.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--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