This is the mail archive of the
insight@sourceware.org
mailing list for the Insight project.
Re: -nx and .gdbtkinit
- From: Bruce Korb <bkorb at gnu dot org>
- To: insight at sourceware dot org
- Cc: Keith Seitz <keiths at redhat dot com>, Andrew STUBBS <andrew dot stubbs at st dot com>, insight at sources dot redhat dot com
- Date: Fri, 18 Nov 2005 15:36:29 -0800
- Subject: Re: -nx and .gdbtkinit
- References: <437DC631.1060609@st.com> <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...]