From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25729 invoked by alias); 5 Apr 2012 16:11:44 -0000 Received: (qmail 25708 invoked by uid 22791); 5 Apr 2012 16:11:40 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,SPF_SOFTFAIL,TW_BJ X-Spam-Check-By: sourceware.org Received: from mtaout22.012.net.il (HELO mtaout22.012.net.il) (80.179.55.172) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 05 Apr 2012 16:11:14 +0000 Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0M2000E00KXMPF00@a-mtaout22.012.net.il> for gdb-patches@sourceware.org; Thu, 05 Apr 2012 19:11:12 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.229.252.114]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0M2000DGXKYNS3J0@a-mtaout22.012.net.il>; Thu, 05 Apr 2012 19:11:12 +0300 (IDT) Date: Thu, 05 Apr 2012 16:11:00 -0000 From: Eli Zaretskii Subject: Re: [patch#2 2/6] set auto-load * main part In-reply-to: <20120403183301.GA13483@host2.jankratochvil.net> To: Jan Kratochvil Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83vcleb1lb.fsf@gnu.org> References: <20120329091121.GC25449@host2.jankratochvil.net> <83iphm1rq1.fsf@gnu.org> <20120403183301.GA13483@host2.jankratochvil.net> 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-04/txt/msg00067.txt.bz2 > Date: Tue, 3 Apr 2012 20:33:01 +0200 > From: Jan Kratochvil > Cc: gdb-patches@sourceware.org > > > > +@node Auto-loading > > > +@section Automatically loading associated files > > > > "@cindex auto-loading" would be good here. > > Done. Therefore also changed now: > @node Python Auto-loading > @subsection Python Auto-loading > @cindex auto-loading, Python > -> > @cindex Python auto-loading, Python Do we really need "Python" twice? > > I suggest "... to prevent @value{GDBN} from reading any auto-loaded files" > > instead. > > I think the meaning is not right now. > > There are three categories of files: > > 1. /etc/gdbinit (system gdbinit) and ~/.gdbinit: > They can be disabled only by -nx. > 2. Current directory .gdbinit > They can be disabled either by -nx or by 'set auto-load local-gdbinit no'. > 3. Files like objfile-gdb.py or libthread_db.so.1 > These can be disabled only by 'set auto-load no' (or more specific variants). > > There exists currently no 'set auto-load system-gdbinit' > or 'set auto-load home-gdbinit' so the option -nx still needs to be used in > some cases. > > Using -nx will not disable for example the objfile-gdb.py loading. > > The current paragraph > > # Be aware that system init file (@pxref{System-wide configuration}) > # and init files from your home directory (@pxref{Home Directory Init File}) > # still get read still get read (as they come from generally trusted > # directories). You could use also the @ref{-nx} option to prevent @value{GDBN} > # from reading any auto-loaded files instead. > > IMO says that -nx will disable even objfile-gdb.py, libthread_db.so.1 etc. > auto-loading. Or at least it is ambiguous in such way. Point taken, but then what _did_ you mean by "very every"? > > > > > +@smallexample > > > +(gdb) info auto-load > > > +gdb-scripts: Loaded Script > > > +Yes /home/user/gdb/gdb-gdb.rc > > > > This is a strange layout, and I'm quite sure it will look wrong in > > Info (as the trailing whitespace won't do what you think). Can you > > show how this display is supposed to look like on the screen? > > The trailing spaces are fixed now. (Trailing spaces appear in GDB output in > general but that is really outside of the scope of this patchset.) > > The table header was not properly aligned for "info auto-load" while it was > right for the specific commands like "info auto-load gdb-scripts". The code is > no longer much nice (introduced there #define INFO_AUTO_LOAD hack) but I agree > the layout looks much better now. > > Fixed therefore also the doc: > > @smallexample > (gdb) info auto-load > gdb-scripts: > Loaded Script > Yes /home/user/gdb/gdb-gdb.gdb > libthread-db: No auto-loaded libthread-db. > local-gdbinit: Local .gdbinit file "/home/user/gdb/.gdbinit" has been loaded. > python-scripts: > Loaded Script > Yes /home/user/gdb/gdb-gdb.py > @end smallexample > > > > > +@multitable {@xref{dotdebug_gdb_scripts section}.} {See @ref{set auto-load python-scripts}} > > > +@item @xref{objfile-gdb.py file}. > > > +@tab See @ref{set auto-load python-scripts}. > > > > Does this table with 2 cross-references on each line look good in the > > Info manual? > > IMO it looks great: > > *Note objfile-gdb.py file::. See *note set auto-load python-scripts::. > *Note objfile-gdb.gdb file::. See *note set auto-load gdb-scripts::. > *Note dotdebug_gdb_scripts section::. See *note set auto-load python-scripts::. > *Note Current Directory Init File::. See *note set auto-load local-gdbinit::. > *Note libthread_db.so.1 file::. See *note set auto-load libthread-db::. > > That "Note" and "note" are excessive there but I could not get rid of them. > I wanted to have there something like @menu but @menu is very special and > I cannot have arbitrary number of @menus inside the @node, moreover to > reference arbitrary @nodes in the document. So I found @multitable to be the > most close to @menu one can get. > > It looks even slightly better in PDF. OK, fine with me.