From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [patch] Implement $_version; for auto-load commands in ~/.gdbinit
Date: Wed, 22 Aug 2012 20:06:00 -0000 [thread overview]
Message-ID: <87y5l6r8rz.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20120821144916.GB28426@host2.jankratochvil.net> (Jan Kratochvil's message of "Tue, 21 Aug 2012 16:49:16 +0200")
>>>>> "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
next prev parent reply other threads:[~2012-08-22 20:06 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 [this message]
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
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=87y5l6r8rz.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--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