From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: jan.kratochvil@redhat.com, gdb-patches@sourceware.org
Subject: Re: [patch#3 5/8] set auto-load safe-path
Date: Wed, 09 May 2012 05:29:00 -0000 [thread overview]
Message-ID: <83ehqt2ac3.fsf@gnu.org> (raw)
In-Reply-To: <20120509042129.GA24867@adacore.com>
> Date: Tue, 8 May 2012 21:21:29 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
>
> I accept the new behavior, and the security claim, no problem.
> I just think that we can improve on the documentation as follow:
>
> In my opinion, we should definitely mention the "auto-load safe-path"
> setting at the very beginning of the auto-load section, before we start
> talking about the various kinds of files that can be automatically
> loaded. And I also think that it would be beneficial to add a reference
> to the safe-path setting in all "set auto-load ..." commands, to make
> sure that people who quickly search the documentation do not miss the
> important fact that setting "auto-load local-gdbinit" to "on" might not
> be sufficient.
>
> And lastly, it would have been nice if, after reading the documentation,
> the user could have had a sense of what policy GDB implements by default.
> For instance, GDB's default policy is to enable auto-loading of all
> files, but only from trusted directories specified via the "auto-load
> safe-path" setting.
I would welcome patches ;-)
next prev parent reply other threads:[~2012-05-09 5:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 19:17 Jan Kratochvil
2012-05-09 4:22 ` Joel Brobecker
2012-05-09 5:29 ` Eli Zaretskii [this message]
2012-05-09 5:54 ` Jan Kratochvil
2012-05-09 12:21 ` Joel Brobecker
2012-05-09 18:26 ` [doc patch] auto-load: Make more set auto-load safe-path references [Re: [patch#3 5/8] set auto-load safe-path] Jan Kratochvil
2012-05-09 18:49 ` Eli Zaretskii
2012-05-09 18:58 ` Jan Kratochvil
2012-05-09 19:58 ` Joel Brobecker
2012-05-11 18:27 ` [commit] " 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=83ehqt2ac3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.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