From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] -iex and -ix: Execute them _after_ gdbinits
Date: Sat, 16 Jun 2012 20:13:00 -0000 [thread overview]
Message-ID: <20120616201312.GA7000@host2.jankratochvil.net> (raw)
In-Reply-To: <83txybdnue.fsf@gnu.org>
On Sat, 16 Jun 2012 22:05:29 +0200, Eli Zaretskii wrote:
> > Date: Sat, 16 Jun 2012 21:54:17 +0200
> > From: Jan Kratochvil <jan.kratochvil@redhat.com>
> >
> > Before 7.5 gets branched/released I would like to yet change behavior of this
> > new feature. The current order is:
> > 1. -iex and -ix
> > 2. /etc/gdbinit, ~/.gdbinit
> > 2. inferior load
> > 3. -ex and -x etc.
> >
> > I would like to swap 1 <-> 2:
> > 1. /etc/gdbinit, ~/.gdbinit
> > 2. -iex and -ix
> > 2. inferior load
> > 3. -ex and -x etc.
>
> That would make it impossible to run a command before loading
> .gdbinit, right?
There is additionally:
4. load .gdbinit from the inferior's directory
If you are in directory ~ then the .gdbinit file is considered to be
~/.gdbinit (and not inferior .gdbinit).
Does it answer your question? Do you see any problem with the new behavior.
> > In practice I found I need to override 'set auto-load safe-path ...' pre-set
> > by ~/.gdbinit for specific GDB runs by -iex. There is no other way to do it.
>
> We could invent some other way of doing that, but without taking away
> what users can do now.
I have not found a use case where the current behavior is better.
> > Contrary to it I cannot imagine why one would want to get -iex commands
> > overriden by /etc/gdbinit and ~/.gdbinit.
>
> Not overriden by, _executed_before_.
I also agree with "executed before" but in practice it means that if distro
for example (Fedora does not) puts into /etc/gdbinit:
set auto-load safe-path /opt:/distro-dir:/bin
Then there is no chance to use -iex 'set auto-load safe-path ...' currently.
(One can use add-auto-load-safe-path everywhere which would work, but then
still one cannot remove/reset directories.)
Thanks,
Jan
next prev parent reply other threads:[~2012-06-16 20:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 19:54 Jan Kratochvil
2012-06-16 20:05 ` Eli Zaretskii
2012-06-16 20:13 ` Jan Kratochvil [this message]
2012-06-16 21:14 ` Eli Zaretskii
2012-06-16 21:32 ` Jan Kratochvil
2012-06-17 2:52 ` Eli Zaretskii
2012-06-17 6:50 ` Jan Kratochvil
2012-06-20 19:01 ` Jan Kratochvil
2012-06-20 19:38 ` Eli Zaretskii
2012-06-22 7:51 ` Jan Kratochvil
2012-06-22 9:44 ` Eli Zaretskii
2012-06-22 11:32 ` Jan Kratochvil
2012-06-22 13:26 ` Eli Zaretskii
2012-06-22 13:48 ` Jan Kratochvil
2012-06-22 14:19 ` Tom Tromey
2012-06-22 14:41 ` Eli Zaretskii
2012-07-02 12:05 ` [commit] " Jan Kratochvil
2012-06-22 14:18 ` Tom Tromey
2012-06-19 7:59 ` Doug Evans
2012-06-22 14:17 ` Tom Tromey
2012-06-18 16:45 ` Joel Brobecker
2012-06-22 14:17 ` Tom Tromey
2012-06-22 16:12 ` Joel Brobecker
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=20120616201312.GA7000@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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