From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8566 invoked by alias); 17 Nov 2005 19:33:31 -0000 Received: (qmail 8556 invoked by uid 22791); 17 Nov 2005 19:33:29 -0000 Received: from nitzan.inter.net.il (HELO nitzan.inter.net.il) (192.114.186.20) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 17 Nov 2005 19:33:29 +0000 Received: from HOME-C4E4A596F7 (IGLD-80-230-21-94.inter.net.il [80.230.21.94]) by nitzan.inter.net.il (MOS 3.6.5-GR) with ESMTP id BYW05435 (AUTH halo1); Thu, 17 Nov 2005 21:33:14 +0200 (IST) Date: Thu, 17 Nov 2005 19:49:00 -0000 Message-Id: From: Eli Zaretskii To: Andrew STUBBS CC: gdb-patches@sources.redhat.com In-reply-to: <437CB049.6060304@st.com> (message from Andrew STUBBS on Thu, 17 Nov 2005 16:31:05 +0000) Subject: Re: [PATCH] -nx-except-gdbtkinit option Reply-to: Eli Zaretskii References: <437B5ED3.70805@st.com> <437CB049.6060304@st.com> Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2005-11/txt/msg00298.txt.bz2 > Date: Thu, 17 Nov 2005 16:31:05 +0000 > From: Andrew STUBBS > Cc: gdb-patches@sources.redhat.com > > > Second, please tell more about the situations when this option could > > be useful. > > The specific case I use it for is in a wrapper utility which calls gdb > as follows (roughly): > > gdb -nx-except-gdbtkinit -d scriptdir -x globalscript \ > -x ~/.gdbinit -x ./.gdbinit ..... > > The purpose is (among other things) to set up transparently (to the > user) a selection of user-defined commands (for connecting and > configuring target boards) which are available to users in the .gdbinit > files. Sorry, I'm still confused. Doesn't GDB normally read ~/.gdbinit and ./.gdbinit? If so, why do you need to use -nx and then load these init files manually? > If -nx is used it has undesirable side effects when using Insight. In case it wasn't clear, it's those ``undesirable side effects'' are what I was asking to describe in some detail. I don't understand what kind of problems it causes. Perhaps those are misfeatures or bugs we need to fix, instead of introducing a new option. > +@item -nx-except-gdbtkinit > +@kindex -nx-except-gdbtkinit > +The same as @samp{-nx} with the difference that it does not prevent > +Insight from loading the settings file @code{.gdbtkinit}. If you are not ^^^^^ `.gdbtkinit' is a file name, so it should have the @file markup, not @code. Other than that, the documentation patch is approved, conditioned on the code patch approval. Thanks.