From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] Add ``Maintenance Commands'' appendix
Date: Tue, 15 Jan 2002 12:19:00 -0000 [thread overview]
Message-ID: <3C448ED5.6070409@cygnus.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1020115095652.23380Q-100000@is>
> On Tue, 15 Jan 2002, Andrew Cagney wrote:
>
>
>> This was suggested long ago as a way of incorporating the maintenance
>> commands (one of those strange GDB interfaces that should be in the user
>> guide but can't be made to fit).
>>
>> Thoughts?
>
>
> I'm for it, but such a change should include moving the few maint
> commands already documented in gdb.texinfo into this appendix.
Found one (there are not too many):
> @cindex negative breakpoint numbers
> @cindex internal @value{GDBN} breakpoints
> @value{GDBN} itself sometimes sets breakpoints in your program for special
> purposes, such as proper handling of @code{longjmp} (in C programs).
> These internal breakpoints are assigned negative numbers, starting with
> @code{-1}; @samp{info breakpoints} does not display them.
>
> You can see these breakpoints with the @value{GDBN} maintenance command
> @samp{maint info breakpoints}.
I guess I snip things here and change the @samp{} to some sort of cross
reference to the maintenance command.
The below being moved to the maintenance section and being the target of
the reference.
> @table @code
> @kindex maint info breakpoints
> @item maint info breakpoints
> Using the same format as @samp{info breakpoints}, display both the
> breakpoints you've set explicitly, and those @value{GDBN} is using for
> internal purposes. Internal breakpoints are shown with negative
> breakpoint numbers. The type column identifies what kind of breakpoint
> is shown:
>
> @table @code
> @item breakpoint
> Normal, explicitly set breakpoint.
>
> @item watchpoint
> Normal, explicitly set watchpoint.
>
> @item longjmp
> Internal breakpoint, used to handle correctly stepping through
> @code{longjmp} calls.
>
> @item longjmp resume
> Internal breakpoint at the target of a @code{longjmp}.
>
> @item until
> Temporary internal breakpoint used by the @value{GDBN} @code{until} command.
>
> @item finish
> Temporary internal breakpoint used by the @value{GDBN} @code{finish} command.
>
> @item shlib events
> Shared library events.
>
> @end table
>
> @end table
Er, how do I do the cross reference bit?
Andrew
next prev parent reply other threads:[~2002-01-15 20:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 21:35 Andrew Cagney
2002-01-14 23:57 ` Eli Zaretskii
2002-01-15 12:19 ` Andrew Cagney [this message]
2002-01-15 12:27 ` Michael Snyder
2002-01-15 21:57 ` Andrew Cagney
2002-01-15 22:11 ` Eli Zaretskii
2002-01-15 22:26 ` Andrew Cagney
2002-01-15 22:52 ` Eli Zaretskii
2002-01-16 7:41 ` Andrew Cagney
2002-01-16 8:33 ` Eli Zaretskii
2002-01-16 12:31 ` Andrew Cagney
2002-01-16 23:36 ` Eli Zaretskii
2002-01-17 15:04 ` Andrew Cagney
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=3C448ED5.6070409@cygnus.com \
--to=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.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