From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, Doug Evans <dje@google.com>
Subject: Re: [patch+7.5] auto-load: User conveniences suggested by Doug Evans
Date: Fri, 24 Aug 2012 15:17:00 -0000 [thread overview]
Message-ID: <50379AE3.6020502@redhat.com> (raw)
In-Reply-To: <20120824151237.GA7200@host2.jankratochvil.net>
On 08/24/2012 04:12 PM, Jan Kratochvil wrote:
> On Wed, 22 Aug 2012 17:46:27 +0200, Pedro Alves wrote:
>> On 08/21/2012 03:43 PM, Jan Kratochvil wrote:
>>> +add \"set auto-load safe-path /\" line to \"%s\".\n\
>>> +For more information about this security protection run from the shell: \
>>> +info \"(gdb)Auto-loading safe path\"\n"),
>>> + filename_real, homeinit, homeinit);
>>
>> This may be cryptic, for instance, for Windows users who won't
>> have 'info' available in the shell. How about something like:
>>
>> For more information about this security protection see the
>> "Auto-loading safe path" section in the GDB manual.
>>
>> ?
>
> In such case I prefer to rather drop the line. It is obvious one can find the
> information in GDB Manual.
I disagree. The sentence says which section to look for. There are many methods
to get at the manual. E.g, a frontend may even have the manual embedded/indexed in
its help system.
> The goal was to make access to the information easy enough.
>
> What about printing instead:
>
> For more information about this security protection see: http://sourceware.org/gdb/onlinedocs/gdb/Auto_002dloading-safe-path.html
This points at the current/trunk version of GDB's docs, not the version that the user is running.
We shouldn't ever assume these urls are stable.
>
>
> Thanks,
> Jan
--
Pedro Alves
next prev parent reply other threads:[~2012-08-24 15:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 14:44 Jan Kratochvil
2012-08-21 17:50 ` Eli Zaretskii
2012-08-24 16:11 ` Jan Kratochvil
2012-08-24 18:15 ` Eli Zaretskii
2012-09-09 8:53 ` Jan Kratochvil
2012-09-09 17:26 ` Eli Zaretskii
2012-09-09 17:55 ` Jan Kratochvil
2012-09-09 18:09 ` Eli Zaretskii
2012-08-22 15:46 ` Pedro Alves
2012-08-24 15:13 ` Jan Kratochvil
2012-08-24 15:17 ` Pedro Alves [this message]
2012-08-24 15:19 ` Eli Zaretskii
2012-08-24 15:28 ` Pedro Alves
2012-08-24 15:31 ` Pedro Alves
2012-08-24 15:43 ` Jan Kratochvil
2012-08-24 17:56 ` Eli Zaretskii
2012-08-24 18:01 ` Jan Kratochvil
2012-08-24 18:26 ` Eli Zaretskii
2012-08-27 18:02 ` Pedro Alves
2012-08-27 18:12 ` Jan Kratochvil
2012-09-09 9:02 ` Jan Kratochvil
2012-09-10 11:29 ` Pedro Alves
2012-09-10 11:47 ` Jan Kratochvil
2012-09-10 13:06 ` Pedro Alves
2012-09-10 15:28 ` Jan Kratochvil
2012-09-17 18:29 ` [commit+7.5] " 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=50379AE3.6020502@redhat.com \
--to=palves@redhat.com \
--cc=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