From: Andrew STUBBS <andrew.stubbs@st.com>
To: insight@sources.redhat.com
Subject: -nx and .gdbtkinit
Date: Fri, 18 Nov 2005 12:19:00 -0000 [thread overview]
Message-ID: <437DC631.1060609@st.com> (raw)
Hi all,
The GDB -nx option currently causes Insight to ignore the .gdbtkinit (or
gdbtk.ini) file.
This is a problem for me because I need to disable .gdbinit, but wish to
continue using .gdbtkinit.
Why is it done this way? I am told .inputrc is always read, no matter what.
Would it be acceptable to totally remove this 'feature'? Or at least
unhook it from -nx somehow?
I had posted an alternative solution (-nx-except-gdbtkinit) to
gdb-patches here
http://sources.redhat.com/ml/gdb-patches/2005-11/msg00233.html, but that
suggestion has not been met with much approval.
Any other suggestions?
Thanks
Andrew Stubbs
next reply other threads:[~2005-11-18 12:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 12:19 Andrew STUBBS [this message]
2005-11-18 22:44 ` Keith Seitz
2005-11-18 23:36 ` Bruce Korb
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=437DC631.1060609@st.com \
--to=andrew.stubbs@st.com \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).