From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Pedro Alves <palves@redhat.com>, "Maucci\,
Cyrille" <cyrille.maucci@hp.com>,
"gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: working around batch mode command errors
Date: Thu, 01 Nov 2012 20:38:00 -0000 [thread overview]
Message-ID: <87pq3xqcse.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CADPb22TsTNNvRxe8TOcQdGNbW6Tp6bK9WZ5j54OgE0RgRRMQig@mail.gmail.com> (Doug Evans's message of "Thu, 1 Nov 2012 13:30:43 -0700")
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> I went looking for the bugzilla entry but couldn't find it.
http://sourceware.org/bugzilla/show_bug.cgi?id=8487
Doug> try:
Doug> gdb.execute (...)
Doug> except:
Doug> pass
Doug> is just too much to type.
Doug> </sarcasm> :-)
:)
We can have both try/catch and ignore-errors, if we want.
Tom
prev parent reply other threads:[~2012-11-01 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 22:28 Maucci, Cyrille
2012-10-30 17:27 ` Jan Kratochvil
2012-10-30 17:39 ` Pedro Alves
2012-10-30 17:43 ` Tom Tromey
2012-11-01 20:30 ` Doug Evans
2012-11-01 20:38 ` Tom Tromey [this message]
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=87pq3xqcse.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=cyrille.maucci@hp.com \
--cc=dje@google.com \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).