From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [patch 1/2] Provide $ddir substitution for --with-auto-load-safe-path
Date: Mon, 14 May 2012 14:57:00 -0000 [thread overview]
Message-ID: <20120514145634.GA30557@host2.jankratochvil.net> (raw)
In-Reply-To: <20120514144950.GD10253@adacore.com>
On Mon, 14 May 2012 16:49:50 +0200, Joel Brobecker wrote:
> Personally, I think it is a complication to have so many settings
> that are paths, and I feel like the only way to get away with it is
> to document exactly the sequence in which each of the setting is being
> evaluated. But I don't have a strong opinion on this.
I find most easy that:
(1) "set auto-load safe-path" is evaluated for any auto-loaded file.
(2) "set auto-load scripts-directory" is evaluted for auto-loaded scripts.
Besides scripts there exist also .gdbinit or libthread-db, more in the future.
One checks "set auto-load safe-path" to verify the path is secure.
One checks "set auto-load scripts-directory" if it does not load some script.
One re-checks "set auto-load safe-path" if GDB refuses to load some file.
Combining these two variables / meanings complicates it for my mind.
Just giving my point of view. Sure I am terribly biased by implementing it.
Regards,
Jan
prev parent reply other threads:[~2012-05-14 14:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 15:47 Jan Kratochvil
2012-05-09 17:43 ` Eli Zaretskii
2012-05-09 18:17 ` [obv doc] Fix too wide @smallexample [Re: [patch 1/2] Provide $ddir substitution for --with-auto-load-safe-path] Jan Kratochvil
2012-05-09 18:48 ` Eli Zaretskii
2012-05-09 18:59 ` [patch 1/2] Provide $ddir substitution for --with-auto-load-safe-path Jan Kratochvil
2012-05-09 20:08 ` Joel Brobecker
2012-05-11 16:46 ` Jan Kratochvil
2012-05-11 17:29 ` Joel Brobecker
2012-05-11 18:15 ` Jan Kratochvil
2012-05-11 18:13 ` Pedro Alves
2012-05-11 18:17 ` Jan Kratochvil
2012-05-11 18:59 ` Pedro Alves
2012-05-11 19:05 ` Jan Kratochvil
2012-05-11 19:15 ` Pedro Alves
2012-05-11 19:34 ` Jan Kratochvil
2012-05-11 20:28 ` [patch] Cosmetic fix 'show auto-load safe-path' for ":" [Re: [patch 1/2] Provide $ddir substitution for --with-auto-load-safe-path] Jan Kratochvil
2012-05-18 17:45 ` [commit] [patch] Cosmetic fix 'show auto-load safe-path' for ":" Jan Kratochvil
2012-05-11 18:19 ` [patch 1/2] Provide $ddir substitution for --with-auto-load-safe-path Joel Brobecker
2012-05-11 18:30 ` Jan Kratochvil
2012-05-11 19:38 ` Joel Brobecker
2012-05-11 19:54 ` Jan Kratochvil
2012-05-14 14:50 ` Joel Brobecker
2012-05-14 14:57 ` Jan Kratochvil [this message]
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=20120514145634.GA30557@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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