From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22084 invoked by alias); 27 Mar 2012 20:33:50 -0000 Received: (qmail 22075 invoked by uid 22791); 27 Mar 2012 20:33:49 -0000 X-SWARE-Spam-Status: No, hits=-6.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,TW_BJ,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 27 Mar 2012 20:33:26 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q2RKXPWR032150 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 27 Mar 2012 16:33:26 -0400 Received: from host2.jankratochvil.net (ovpn-116-28.ams2.redhat.com [10.36.116.28]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q2RKXL7x004483 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Tue, 27 Mar 2012 16:33:24 -0400 Date: Tue, 27 Mar 2012 20:33:00 -0000 From: Jan Kratochvil To: gdb-patches@sourceware.org Subject: [doc patch] Move @menu to end of @node (Auto-loading) Message-ID: <20120327203321.GA28113@host2.jankratochvil.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-03/txt/msg00925.txt.bz2 Hi Eli, info '(texinfo)Menu Location' # A menu must be located at the end of a node, without any regular text # or additional commands between the `@end menu' and the beginning of the # next node. (As a consequence, there may be at most one menu in a node.) # # This is actually a useful restriction, since a reader who uses the # menu could easily miss any such text. Technically, it is necessary # because in Info format, there is no marker for the end of a menu, so # Info-reading programs would have no way to know when the menu ends and # normal text resumes. This is violated at multiple places in gdb.texinfo. But I see no problem from that, info command displays it properly, also tested PDF (no menus) and HTML (working menus). So maybe I can just drop this patch, the menu looks better in the first part. Thanks, Jan gdb/doc/ 2012-03-27 Jan Kratochvil * gdb.texinfo (Auto-loading): Move @menu to the end of @node. Create two new links fir 'objfile-gdb.py file' and 'dotdebug_gdb_scripts section'. --- ./gdb/doc/gdb.texinfo 27 Mar 2012 20:15:20 -0000 1.937 +++ ./gdb/doc/gdb.texinfo 27 Mar 2012 20:28:30 -0000 @@ -24714,13 +24714,9 @@ writable. When a new object file is read (for example, due to the @code{file} command, or because the inferior has loaded a shared library), @value{GDBN} will look for Python support scripts in several ways: -@file{@var{objfile}-gdb.py} and @code{.debug_gdb_scripts} section. - -@menu -* objfile-gdb.py file:: The @file{@var{objfile}-gdb.py} file -* dotdebug_gdb_scripts section:: The @code{.debug_gdb_scripts} section -* Which flavor to choose?:: -@end menu +@file{@var{objfile}-gdb.py} (@pxref{objfile-gdb.py file}) +and @code{.debug_gdb_scripts} section +(@pxref{dotdebug_gdb_scripts section}). The auto-loading feature is useful for supplying application-specific debugging commands and scripts. @@ -24767,6 +24763,12 @@ When reading an auto-loaded file, @value function (@pxref{Objfiles In Python}). This can be useful for registering objfile-specific pretty-printers. +@menu +* objfile-gdb.py file:: The @file{@var{objfile}-gdb.py} file +* dotdebug_gdb_scripts section:: The @code{.debug_gdb_scripts} section +* Which flavor to choose?:: +@end menu + @node objfile-gdb.py file @subsubsection The @file{@var{objfile}-gdb.py} file @cindex @file{@var{objfile}-gdb.py}