From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6448 invoked by alias); 15 Jan 2002 20:19:36 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 6415 invoked from network); 15 Jan 2002 20:19:35 -0000 Received: from unknown (HELO localhost.cygnus.com) (216.138.202.10) by sources.redhat.com with SMTP; 15 Jan 2002 20:19:35 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.cygnus.com (Postfix) with ESMTP id CC0273D2E; Tue, 15 Jan 2002 15:19:33 -0500 (EST) Message-ID: <3C448ED5.6070409@cygnus.com> Date: Tue, 15 Jan 2002 12:19:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.7) Gecko/20020103 X-Accept-Language: en-us MIME-Version: 1.0 To: Eli Zaretskii Cc: gdb-patches@sources.redhat.com Subject: Re: [rfa] Add ``Maintenance Commands'' appendix References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-01/txt/msg00429.txt.bz2 > 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