This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] Implement $_version; for auto-load commands in ~/.gdbinit
- From: Tom Tromey <tromey at redhat dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: gdb-patches at sourceware dot org, Eli Zaretskii <eliz at gnu dot org>
- Date: Wed, 22 Aug 2012 14:06:40 -0600
- Subject: Re: [patch] Implement $_version; for auto-load commands in ~/.gdbinit
- References: <20120821144916.GB28426@host2.jankratochvil.net>
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> One solution would be some new mode where errors are only printed
Jan> and script execution does not stop there.
I think that would be preferable. It is better to test features rather
than versions.
It is trivial to write an 'ignore-errors' in python, or C for that matter.
Or you could resurrect the old try-catch patch for the CLI that is
languishing in bugzilla.
Jan> I have implemented a way to explicitly check for GDB version instead.
The problem I see is that distros often ship new features but can't
assign a meaningful new version number.
Tom