From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andrew STUBBS <andrew.stubbs@st.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] -nx-except-gdbtkinit option
Date: Thu, 17 Nov 2005 23:44:00 -0000 [thread overview]
Message-ID: <20051117194639.GA20312@nevyn.them.org> (raw)
In-Reply-To: <ur79f5ate.fsf@gnu.org>
On Thu, Nov 17, 2005 at 09:33:17PM +0200, Eli Zaretskii wrote:
> > 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?
In order for the global script to be loaded before .gdbinit, I think.
> > 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.
It sounds like there's no GDB command to process .gdbtkinit, which is a
TCL file rather than a GDB CLI script file. Andrew, is that right? If
so, have you considered adding such a command to Insight, instead?
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-11-17 19:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 17:34 Andrew STUBBS
2005-11-16 22:43 ` Eli Zaretskii
2005-11-17 19:20 ` Andrew STUBBS
2005-11-17 19:49 ` Eli Zaretskii
2005-11-17 23:44 ` Daniel Jacobowitz [this message]
2005-11-18 2:52 ` Andrew STUBBS
2005-11-18 12:33 ` Andrew STUBBS
2005-11-18 12:50 ` Eli Zaretskii
2005-11-18 12:59 ` Andrew STUBBS
2005-11-18 16:33 ` Daniel Jacobowitz
2005-11-30 1:38 ` Andrew STUBBS
2005-11-18 0:08 ` Andrew STUBBS
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051117194639.GA20312@nevyn.them.org \
--to=drow@false.org \
--cc=andrew.stubbs@st.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox