From: Pedro Alves <palves@redhat.com>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: Daniel Jacobowitz <drow@false.org>,
gdb-patches@sourceware.org,
Richard Sandiford <rdsandiford@googlemail.com>
Subject: Re: gdb_test_multiple and empty $message
Date: Thu, 26 Apr 2012 13:34:00 -0000 [thread overview]
Message-ID: <4F994C1C.7050002@redhat.com> (raw)
In-Reply-To: <4F99491E.8050605@redhat.com>
On 04/26/2012 02:09 PM, Pedro Alves wrote:
>> Are these meant to trigger where both the command and the message supplied
>> are empty?
I meant to say that I don't think I ever saw such usage, and indeed I can't
find any now. Thinking a bit more, it could be conceivable to hide
a fail call in that case, and handle the error at the caller, by
inspecting gdb_test_multiple's result, but I'm not really sure that's
useful. So I'd also be fine with making all the fails consistent and
documenting this, if people want it.
--
Pedro Alves
next prev parent reply other threads:[~2012-04-26 13:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 22:36 [RFA] MIPS/GDB: Fix the handling of MIPS16 thunks Maciej W. Rozycki
2012-04-11 19:16 ` Richard Sandiford
2012-04-12 13:09 ` Maciej W. Rozycki
2012-04-12 19:39 ` Richard Sandiford
2012-04-13 20:46 ` Maciej W. Rozycki
2012-04-20 14:54 ` Pedro Alves
2012-04-20 16:01 ` Maciej W. Rozycki
2012-04-21 18:55 ` Daniel Jacobowitz
2012-04-26 0:10 ` Maciej W. Rozycki
2012-04-26 13:10 ` Pedro Alves
2012-04-26 17:27 ` Maciej W. Rozycki
2012-04-26 13:23 ` gdb_test_multiple and empty $message Pedro Alves
2012-04-26 13:34 ` Pedro Alves [this message]
2012-04-26 14:31 ` Tom Tromey
2012-04-26 14:42 ` Joel Brobecker
2012-04-27 20:23 ` Maciej W. Rozycki
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=4F994C1C.7050002@redhat.com \
--to=palves@redhat.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@codesourcery.com \
--cc=rdsandiford@googlemail.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