Stepping off breakpoints in non-stop debugging mode (resubmit)

[Pedro Alves]

A Thursday 10 April 2008 04:12:40, Eli Zaretskii wrote:
> > From: Pedro Alves <pedro@codesourcery.com>
> > Date: Thu, 10 Apr 2008 00:03:05 +0100
> >
> > Does it look OK to apply after Vlad's patch has gone in?
>
> The documentation needs more work.  It needs to explain what is
> "displaced stepping".  Without such an explanation, the text you wrote
> simply cannot make sense to the reader.
>

How about this?

@kindex maint set can-use-displaced-stepping
@kindex maint show can-use-displaced-stepping
@cindex displaced stepping support
@item maint set can-use-displaced-stepping
@itemx maint show can-use-displaced-stepping
Control whether or not @value{GDBN} will do displaced stepping if the
target supports it.  The default is on.  Displaced stepping is a way
to single-step over breakpoints without removing them from the
inferior, by executing an out-of-line copy of the instruction under
the breakpoint.  It is also known as out-of-line single-stepping.


> Also, this:
> > +Displays the current state of @value{GDBN} displaced stepping
> > +debugging info.
>
> leaves me wondering what is meant by ``the state ... of info''.  How
> can info have a state?
>

I was trying to follow the trend here:

 @item show debug serial
 Displays the current state of displaying @value{GDBN} serial debugging
 info.

 @item show debug target
 Displays the current state of displaying @value{GDBN} target debugging
 info.

 (etc.)

Turns out I'm not a great follower.  I happened to miss the
"displaying" word.  Should be:

 +Displays the current state of displaying @value{GDBN} displaced stepping
 +debugging info.

A couple of typos were also fixed in comments.  Updated
patch attached.

-- 
Pedro Alves
-------------- next part --------------
A non-text attachment was scrubbed...
Name: displaced_stepping.diff
Type: text/x-diff
Size: 66292 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20080410/04441200/attachment.bin>