From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch, doc RFA] New command-line option -na.
Date: Mon, 13 Dec 2010 19:28:00 -0000 [thread overview]
Message-ID: <AANLkTi=SSzhYzc96Zk12yLCWFaCDiw0s+Nooc_V1N2R4@mail.gmail.com> (raw)
In-Reply-To: <20101213185543.GB29492@host0.dyn.jankratochvil.net>
On Mon, Dec 13, 2010 at 10:55 AM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> On Sat, 11 Dec 2010 01:47:34 +0100, Doug Evans wrote:
>> The capability exists today with "maint set python auto-load on|off",
>> but that can't be used to disable scripts from a program provided on
>> the command line.
>> In order to use that, one has to start gdb without a program,
>> disable auto-loading, and *then* use the "file" command. Bleah.
>
> I use the "file" trick commonly for example for:
> gdb -ex 'set debug-file-directory /tmp/foo:/usr/lib/debug' -ex 'file /bin/date'
>
>
>> I'm renaming "maint set python auto-load on|off" to
>> "set auto-load-scripts on|off".
>
> I would find this part as a sufficient one. Otherwise we should introduce
> a command-line option also for "debug-file-directory" and probably others.
> Do you find a common need for `-na'?
The high order bit is the change to the option name.
I wonder if it'd be sufficiently useful to provide support for adding
new command-line options in python.
Then I could add -na in system.gdbinit.
next prev parent reply other threads:[~2010-12-13 19:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-11 0:47 Doug Evans
2010-12-11 8:16 ` Eli Zaretskii
2010-12-15 1:40 ` Doug Evans
2010-12-15 6:05 ` Eli Zaretskii
2010-12-15 6:26 ` Doug Evans
2010-12-15 6:58 ` Eli Zaretskii
2010-12-15 7:09 ` Doug Evans
2010-12-13 18:55 ` Jan Kratochvil
2010-12-13 19:28 ` Doug Evans [this message]
2010-12-13 19:36 ` Doug Evans
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='AANLkTi=SSzhYzc96Zk12yLCWFaCDiw0s+Nooc_V1N2R4@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