From: Bruce Korb <bkorb@gnu.org>
To: insight@sourceware.org
Cc: Keith Seitz <keiths@redhat.com>,
Andrew STUBBS <andrew.stubbs@st.com>,
insight@sources.redhat.com
Subject: Re: -nx and .gdbtkinit
Date: Fri, 18 Nov 2005 23:36:00 -0000 [thread overview]
Message-ID: <200511181536.30158.bkorb@gnu.org> (raw)
In-Reply-To: <437E5954.60104@redhat.com>
What is the processing order of these files?
Another way of putting it: could not the ``-nx'' option be
added to the .gdbtkinit file and cause it to inhibit .gdbinit?
I stubbed my toe on this some time back and it did take some
bother to "get it right".....
Cheers - Bruce
On Friday 18 November 2005 02:44 pm, Keith Seitz wrote:
> Andrew STUBBS wrote:
>
> > The GDB -nx option currently causes Insight to ignore the .gdbtkinit (or
> > gdbtk.ini) file.
>
> Correct.
>
> > This is a problem for me because I need to disable .gdbinit, but wish to
> > continue using .gdbtkinit.
>
> Eeew... Ummm... Hmmm...
> > Would it be acceptable to totally remove this 'feature'? Or at least
> > unhook it from -nx somehow?
>
> Yeah, I think you should be able to do something for insight. The
> problem is adding new command-line options to gdb for insight will be
> problematic (to be polite), since gdb still greedily hoards all options
> processing. [I once started building a patch to separate this out...]
WARNING: multiple messages have this Message-ID
From: Bruce Korb <bkorb@gnu.org>
To: insight@sourceware.org
Cc: Keith Seitz <keiths@redhat.com>,
Andrew STUBBS <andrew.stubbs@st.com>,
insight@sources.redhat.com
Subject: Re: -nx and .gdbtkinit
Date: Sat, 19 Nov 2005 00:14:00 -0000 [thread overview]
Message-ID: <200511181536.30158.bkorb@gnu.org> (raw)
Message-ID: <20051119001400.7YrAYPg5bv-ksX3nD6GjPupc4GJ0UUZnZRCPmyAmlRM@z> (raw)
In-Reply-To: <437E5954.60104@redhat.com>
What is the processing order of these files?
Another way of putting it: could not the ``-nx'' option be
added to the .gdbtkinit file and cause it to inhibit .gdbinit?
I stubbed my toe on this some time back and it did take some
bother to "get it right".....
Cheers - Bruce
On Friday 18 November 2005 02:44 pm, Keith Seitz wrote:
> Andrew STUBBS wrote:
>
> > The GDB -nx option currently causes Insight to ignore the .gdbtkinit (or
> > gdbtk.ini) file.
>
> Correct.
>
> > This is a problem for me because I need to disable .gdbinit, but wish to
> > continue using .gdbtkinit.
>
> Eeew... Ummm... Hmmm...
> > Would it be acceptable to totally remove this 'feature'? Or at least
> > unhook it from -nx somehow?
>
> Yeah, I think you should be able to do something for insight. The
> problem is adding new command-line options to gdb for insight will be
> problematic (to be polite), since gdb still greedily hoards all options
> processing. [I once started building a patch to separate this out...]
next prev parent reply other threads:[~2005-11-18 23:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 12:19 Andrew STUBBS
2005-11-18 22:44 ` Keith Seitz
2005-11-18 23:36 ` Bruce Korb [this message]
2005-11-19 0:14 ` Bruce Korb
2005-11-19 16:01 ` Keith Seitz
2005-11-21 19:35 ` Andrew STUBBS
2005-11-24 18:54 ` Andrew STUBBS
2005-11-21 11:56 ` Andrew STUBBS
2005-11-28 18:50 ` Keith Seitz
2005-11-29 11:12 ` [PATCH] INSIGHT_FORCE_READ_PREFERENCES Andrew STUBBS
2005-12-04 0:01 ` Keith Seitz
2005-12-04 0:53 ` 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=200511181536.30158.bkorb@gnu.org \
--to=bkorb@gnu.org \
--cc=andrew.stubbs@st.com \
--cc=insight@sources.redhat.com \
--cc=insight@sourceware.org \
--cc=keiths@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).