From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2165 invoked by alias); 12 May 2012 09:02:46 -0000 Received: (qmail 2151 invoked by uid 22791); 12 May 2012 09:02:44 -0000 X-SWARE-Spam-Status: No, hits=-6.2 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,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; Sat, 12 May 2012 09:02:31 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q4C92Vpb019656 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sat, 12 May 2012 05:02:31 -0400 Received: from host2.jankratochvil.net (ovpn-116-17.ams2.redhat.com [10.36.116.17]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id q4C92RDl007773 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Sat, 12 May 2012 05:02:30 -0400 Date: Sat, 12 May 2012 09:02:00 -0000 From: Jan Kratochvil To: gdb-patches@sourceware.org Subject: [doc patch] Use plural for global debug info dir(s) Message-ID: <20120512090227.GA20327@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-05/txt/msg00471.txt.bz2 Hi Eli, since commit 36ae52d16cc9d38cfe317a79bb5d63c624359154 Author: Jan Kratochvil Date: Mon Nov 2 14:59:48 2009 +0000 GDB supports multiple paths specified in 'set debug-file-directory'. Documentation is still inconsistent in this regard. Thanks, Jan gdb/doc/ 2012-05-12 Jan Kratochvil * gdb.texinfo (Separate Debug Files): Use plural form for global debugging information directory. diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 38ef079..d927b92 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -16201,7 +16201,7 @@ Show whether a source file may have multiple base names. @cindex debugging information in separate files @cindex @file{.debug} subdirectories @cindex debugging information directory, global -@cindex global debugging information directory +@cindex global debugging information directories @cindex build ID, and separate debugging files @cindex @file{.build-id} directory @@ -16247,12 +16247,12 @@ uses two different methods of looking for the debug file: For the ``debug link'' method, @value{GDBN} looks up the named file in the directory of the executable file, then in a subdirectory of that directory named @file{.debug}, and finally under the global debug -directory, in a subdirectory whose name is identical to the leading +directories, in a subdirectory whose name is identical to the leading directories of the executable's absolute file name. @item For the ``build ID'' method, @value{GDBN} looks in the -@file{.build-id} subdirectory of the global debug directory for a file +@file{.build-id} subdirectory of the global debug directories for a file named @file{@var{nn}/@var{nnnnnnnn}.debug}, where @var{nn} are the first 2 hex characters of the build ID bit string, and @var{nnnnnnnn} are the rest of the bit string. (Real build ID strings are 32 or more @@ -16262,7 +16262,7 @@ hex characters, not 10.) So, for example, suppose you ask @value{GDBN} to debug @file{/usr/bin/ls}, which has a debug link that specifies the file @file{ls.debug}, and a build ID whose value in hex is -@code{abcdef1234}. If the global debug directory is +@code{abcdef1234}. If the global debug directories path component is @file{/usr/lib/debug}, then @value{GDBN} will look for the following debug information files, in the indicated order: @@ -16277,7 +16277,7 @@ debug information files, in the indicated order: @file{/usr/lib/debug/usr/bin/ls.debug}. @end itemize -You can set the global debugging info directory's name, and view the +You can set the global debugging info directories, and view the name @value{GDBN} is currently using. @table @code