From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] New option -nh: disable loading ~/.gdbinit
Date: Fri, 21 Sep 2012 16:23:00 -0000 [thread overview]
Message-ID: <CADPb22TkCV6LL3qu0g0cYDK8QcfUUxmKWkPcTO7UPjDTiYV88w@mail.gmail.com> (raw)
In-Reply-To: <20120921153508.GA29943@host2.jankratochvil.net>
On Fri, Sep 21, 2012 at 8:35 AM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> On Fri, 21 Sep 2012 00:01:54 +0200, dje@google.com wrote:
>> When running tests (not necessarily tests in gdb/testsuite!) with a
>> gdb with a non-trivial system.gdbinit,
>> it is useful to be able disable loading ~/.gdbinit.
>> system.gdbinit is still necessary, it provides necessary functionality.
>>
>> One *could* run the tests with -nx -x /path/to/system.gdbinit,
>> but the path to system.gdbinit is not necessarily easy to obtain.
>>
>> Instead, I'd like to add this option: -nh.
>
> The current auto-load functionality:
> (gdb) set auto-load
> gdb-scripts local-gdbinit safe-path
> libthread-db python-scripts scripts-directory
>
> besides local-gdbinit would logically have also system-gdbinit and
> home-gdbinit.
>
> -nx would be then equivalent to all of:
> -iex 'set auto-load system-gdbinit off'
> -iex 'set auto-load home-gdbinit off'
> -iex 'set auto-load local-gdbinit off'
>
> -nh would be then equivalent to:
> -iex 'set auto-load home-gdbinit off'
>
> Wouldn't be the last option more clear than another magic option '-nh'?
magic? Say what?
> The patch would be short, I could even post it but so far it was more just
> some sort of a clean-up but if you even have a use for it.
In this case I like the short -nh.
next prev parent reply other threads:[~2012-09-21 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 22:02 dje
2012-09-21 15:23 ` Joel Brobecker
2012-09-21 15:35 ` Jan Kratochvil
2012-09-21 16:23 ` Doug Evans [this message]
2012-09-21 16:28 ` Jan Kratochvil
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=CADPb22TkCV6LL3qu0g0cYDK8QcfUUxmKWkPcTO7UPjDTiYV88w@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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