Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>, dje@google.com
Subject: Re: [patch+7.5] auto-load: User conveniences suggested by Doug Evans
Date: Fri, 24 Aug 2012 15:43:00 -0000	[thread overview]
Message-ID: <20120824154325.GB7200@host2.jankratochvil.net> (raw)
In-Reply-To: <50379E50.6090602@redhat.com>

On Fri, 24 Aug 2012 17:31:28 +0200, Pedro Alves wrote:
> ... and I'd be happy if we combined Jan's and my suggestions.  Something like:
> 
> For more information about this security protection see the
> "Auto-loading safe path" section in the GDB manual.
> For example, run from the shell:
> info \"(gdb)Auto-loading safe path\
> 
> Would that work?

In fact I find this a distribution specific part, which current FSF GDB does
not address and it may never should be.

What about printing in FSF GDB:
	For more information about this security protection see the
	"Auto-loading safe path" section in the GDB manual.

And in Fedora GDB to patch it for:
	For example, run from the shell: info "(gdb)Auto-loading safe path"

As Fedora could also address the common problem of uninstalled gdb-doc and
therefore depending on 'rpm -q gdb-doc' exit code Fedora could print:
	For example, run from the shell: yum -y install gdb-doc; info "(gdb)Auto-loading safe path"

Sure Fedora is unrelated to this gdb-patches list, just giving the picture how
distro specific parts can be useful and at the same time very unrelated to FSF
GDB.


Thanks,
Jan


  reply	other threads:[~2012-08-24 15:43 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
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 [this message]
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=20120824154325.GB7200@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=dje@google.com \
    --cc=eliz@gnu.org \
    --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