Re: [rfa] Add ``Maintenance Commands'' appendix

[Andrew Cagney <ac131313 at cygnus dot com>]

> Date: Wed, 16 Jan 2002 10:40:56 -0500
>> From: Andrew Cagney <ac131313@cygnus.com>
>> 
>> Ah.  Don't forget we're (I'm?) ment to be replacing that with makeinfo 
>> 4.something.somethingextra.
> 
> 
> Yes, the latest version of Texinfo 4.0d (available from
> alpha.gnu.org) supports split-HTML mode, so we could switch.  In that
> case, @anchor is certainly an option.


Hmm, @anchor ...

Attached is a revised patch.  It moves the ``maint info breakpoints'' 
and adds a reference.  it appears to work with texinfo 4.0*, texi2html 
(1.64) and pdftex.  How does it look?

Regarding a switch to ``makeinfo --html'' I think I'll put it on hold. 
I gave it a quick trial but tripped up on two points: I couldn't figure 
out where exactly it was putting the generated files (it wanted a 
gdb.html/ directory but put only index.html in it);  I found the 
generated pages too fine grained (down to a section not chapter).

enjoy,
Andrew
2002-01-16  Andrew Cagney  <ac131313@redhat.com>

	* gdb.texinfo 	(Maintenance Commands): Add appendix.
	(Set Breaks): Copy ``maint info breakpoint'' doco to
	``Maintenance Commands'' appendix.  Add reference.

Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.70
diff -p -r1.70 gdb.texinfo
*** gdb.texinfo	2002/01/11 20:24:14	1.70
--- gdb.texinfo	2002/01/16 20:20:38
*************** Copyright (C) 1988-2001 Free Software Fo
*** 149,154 ****
--- 149,155 ----
  * Command Line Editing::        Command Line Editing
  * Using History Interactively:: Using History Interactively
  * Installing GDB::              Installing GDB
+ * Maintenance Commands::        Maintenance Commands
  * Index::                       Index
  @end menu
  
*************** the breakpoints are conditional, this is
*** 2627,2675 ****
  
  @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}.
! 
! @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
  
  
  @node Set Watchpoints
--- 2628,2639 ----
  
  @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} (@pxref{maint info breakpoints}).
  
  
  @node Set Watchpoints
*************** There is no convenient way to generate a
*** 14850,14855 ****
--- 14814,14864 ----
  
  There are many other options available as well, but they are generally
  needed for special purposes only.
+ 
+ @node Maintenance Commands
+ @appendix Maintenance Commands
+ @cindex maintenance commands
+ @cindex internal commands
+ 
+ In addition to commands intended for @value{GDBN} users, @value{GDBN}
+ includes a number of commands intended for @value{GDBN} developers.
+ These commands are provided here for reference.
+ 
+ @table @code
+ @kindex maint info breakpoints
+ @item @anchor{maint info breakpoints}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
  
  @node Index
  @unnumbered Index