This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: gdb_test_multiple and empty $message

From: Pedro Alves <palves at redhat dot com>
To: "Maciej W. Rozycki" <macro at codesourcery dot com>
Cc: Daniel Jacobowitz <drow at false dot org>, gdb-patches at sourceware dot org, Richard Sandiford <rdsandiford at googlemail dot com>
Date: Thu, 26 Apr 2012 14:22:36 +0100
Subject: Re: gdb_test_multiple and empty $message
References: <alpine.DEB.1.10.1204052320140.19835@tp.orcam.me.uk> <4F916F9E.6040209@redhat.com> <alpine.DEB.1.10.1204201519120.19835@tp.orcam.me.uk> <alpine.DEB.1.10.1204252007360.19835@tp.orcam.me.uk> <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

References:
- [RFA] MIPS/GDB: Fix the handling of MIPS16 thunks
  - From: Maciej W. Rozycki
- Re: [RFA] MIPS/GDB: Fix the handling of MIPS16 thunks
  - From: Pedro Alves
- Re: [RFA] MIPS/GDB: Fix the handling of MIPS16 thunks
  - From: Maciej W. Rozycki
- Re: [RFA] MIPS/GDB: Fix the handling of MIPS16 thunks
  - From: Maciej W. Rozycki
- gdb_test_multiple and empty $message
  - From: Pedro Alves

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]