From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13126 invoked by alias); 26 Apr 2012 13:23:12 -0000 Received: (qmail 13116 invoked by uid 22791); 26 Apr 2012 13:23:10 -0000 X-SWARE-Spam-Status: No, hits=-7.4 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 26 Apr 2012 13:22:44 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q3QDMcC9014405 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 26 Apr 2012 09:22:38 -0400 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id q3QDMau1001304; Thu, 26 Apr 2012 09:22:37 -0400 Message-ID: <4F994C1C.7050002@redhat.com> Date: Thu, 26 Apr 2012 13:34:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120329 Thunderbird/11.0.1 MIME-Version: 1.0 To: "Maciej W. Rozycki" CC: Daniel Jacobowitz , gdb-patches@sourceware.org, Richard Sandiford Subject: Re: gdb_test_multiple and empty $message References: <4F916F9E.6040209@redhat.com> <4F99491E.8050605@redhat.com> In-Reply-To: <4F99491E.8050605@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-04/txt/msg00902.txt.bz2 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