Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: drow@false.org, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Keep breakpoints always inserted.
Date: Sat, 15 Mar 2008 15:10:00 -0000	[thread overview]
Message-ID: <uabl0hvm5.fsf@gnu.org> (raw)
In-Reply-To: <200803151312.15051.vladimir@codesourcery.com>

> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Sat, 15 Mar 2008 13:12:14 +0300
> Cc: gdb-patches@sources.redhat.com
> 
> I've added NEW and documentation.

Thanks.

> +set breakpoint always-inserted
> +show breakpoint always-inserted
> +  Keep breakpoints always inserted in the target.

This entry is not detailed enough to be useful.  Please keep in mind
that GDB users are not necessarily aware of the fact that GDB removes
the breakpoints whenever the inferior stops and reinserts them before
resuming it.

> +By default, @value{GDBN} inserts breakpoints in the target only when
> +resuming the target, and removes breakpoints whenever the target stop.
                                                                    ^^^^
"stops".

> +This behaviour guards against leaving breakpoints inserted in the
> +target should gdb abrubptly disconnect, which is possible with remote
> +targets.

Without explaining that a breakpoint replaces a portion of code with a
breakpoint instruction, the reader will not understand what is
dangerous about this.

>                      This bevaious can be controlled with the following
                            ^^^^^^^^
You mean "behavior", right?

> +This is the default behaviour.  All breakpoints, including newly added
                       ^^^^^^^^^
Please use the US spelling ("behavior"), for consistency.

> +@item set breakpoint always-inserted on
> +Causes all breakpoints to be inserted in the target at all times.  If
> +the user adds a new breakpoint, or changes an existing breakpoint, the
> +breakpoints in the target are updated immediately.  A breakpoint is
> +removed from the target only when breakpoint itself is removed.

It would be good to give the reader a hint when this behavior is
useful.

Otherwise, okay with me.


  reply	other threads:[~2008-03-15 15:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-28 14:18 Vladimir Prus
2008-03-10 21:09 ` Daniel Jacobowitz
2008-03-14 20:22   ` Vladimir Prus
2008-03-15 10:13   ` Vladimir Prus
2008-03-15 15:10     ` Eli Zaretskii [this message]
2008-04-02 13:02       ` Vladimir Prus
2008-04-02 18:18         ` Eli Zaretskii
2008-03-17 22:21     ` Daniel Jacobowitz
2008-03-18  4:15       ` Eli Zaretskii
2008-03-18  6:06         ` Vladimir Prus
2008-04-03 18:10       ` Vladimir Prus
2008-04-07 15:32         ` Daniel Jacobowitz
2008-04-09 23:45           ` Vladimir Prus
2008-04-10  8:16             ` Luis Machado
2008-04-17 16:50             ` Daniel Jacobowitz
2008-04-23 21:18               ` Pedro Alves
2008-04-23 21:24                 ` Daniel Jacobowitz
2008-04-24 11:22                   ` Vladimir Prus
2008-04-24 12:10                     ` Vladimir Prus

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=uabl0hvm5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@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