From: Andrew STUBBS <andrew.stubbs@st.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] -nx-except-gdbtkinit option
Date: Fri, 18 Nov 2005 00:08:00 -0000 [thread overview]
Message-ID: <437CDE3A.3010701@st.com> (raw)
In-Reply-To: <ur79f5ate.fsf@gnu.org>
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?
I want the .gdbinit files loaded after the mystical 'globalscript' file.
Then they can use commands defined by that script.
>>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.
Without this file Insight does not remember any of your settings, such
as window size and position, target settings and breakpoints.
> `.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.
Thanks
Andrew
prev parent reply other threads:[~2005-11-17 19:49 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
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 [this message]
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=437CDE3A.3010701@st.com \
--to=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