From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [patch] Implement $_version; for auto-load commands in ~/.gdbinit
Date: Fri, 24 Aug 2012 18:50:00 -0000 [thread overview]
Message-ID: <83393cgm5w.fsf@gnu.org> (raw)
In-Reply-To: <20120824182524.GA15099@host2.jankratochvil.net>
> Date: Fri, 24 Aug 2012 20:25:24 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: tromey@redhat.com, gdb-patches@sourceware.org
>
> On Fri, 24 Aug 2012 20:20:48 +0200, Eli Zaretskii wrote:
> > I fail to see how this is better than using $_version.
>
> GNU gdb (GDB) Fedora (7.3.50.20110722-16.fc16)
> [...]
> (gdb) show auto-load safe-path
> List of directories from which it is safe to auto-load files is [...].
>
> And this is even not yet GDB 7.4. And for RHELs the security backport will be
> for even older GDBs.
But all this stuff we are discussing is for the user, not for the
distributor. A user always knows which version(s) she uses, so she
can set the minimum versions accordingly.
And if worse comes to worst, one can always be conservative. It's not
a disaster not to invoke a command that was back-ported.
I find the alternatives more complex and not much more useful.
next prev parent reply other threads:[~2012-08-24 18:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 14:49 Jan Kratochvil
2012-08-21 17:59 ` Eli Zaretskii
2012-08-21 21:32 ` Doug Evans
2012-08-22 20:06 ` Tom Tromey
2012-08-23 18:05 ` Pedro Alves
2012-08-24 16:32 ` Jan Kratochvil
2012-08-24 16:39 ` Jan Kratochvil
2012-08-24 16:54 ` dje
2012-08-24 16:57 ` Jan Kratochvil
2012-08-24 18:12 ` Doug Evans
2012-08-24 17:41 ` Tom Tromey
2012-08-24 17:50 ` Jan Kratochvil
2012-08-24 18:00 ` Tom Tromey
2012-08-24 18:20 ` Eli Zaretskii
2012-08-24 18:26 ` Jan Kratochvil
2012-08-24 18:50 ` Eli Zaretskii [this message]
2012-08-24 19:00 ` Jan Kratochvil
2012-08-24 19:03 ` Eli Zaretskii
2012-09-02 15:12 ` Joel Brobecker
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=83393cgm5w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=tromey@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