From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23103 invoked by alias); 25 Aug 2015 18:31:19 -0000 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 Received: (qmail 23087 invoked by uid 89); 25 Aug 2015 18:31:17 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Tue, 25 Aug 2015 18:31:16 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (Postfix) with ESMTPS id 7CCA88EA52 for ; Tue, 25 Aug 2015 18:31:15 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t7PIVEWt003897; Tue, 25 Aug 2015 14:31:14 -0400 Message-ID: <55DCB471.4020103@redhat.com> Date: Tue, 25 Aug 2015 18:31:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Sergio Durigan Junior CC: GDB Patches Subject: Re: [PATCH] Increase timeout on gdb.base/exitsignal.exp References: <1440481342-25971-1-git-send-email-sergiodj@redhat.com> <55DC46C5.4050808@redhat.com> <87si77gr9x.fsf@redhat.com> In-Reply-To: <87si77gr9x.fsf@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2015-08/txt/msg00735.txt.bz2 On 08/25/2015 07:24 PM, Sergio Durigan Junior wrote: >> This (many instances) doesn't make sense to me. And I think wouldn't >> fix anything. Seems to me the bumped timeout, if any, should be around >> the continue that caused the first time out: >> >> # Continue until the end. >> gdb_test "continue" "Program terminated with signal SIGSEGV.*" \ >> "program terminated with SIGSEGV" > > Sorry, I am confused... The timeout does not occur on this command: it > occurs on the print commands. So I think we must extend the timeout for > the print commands; don't we? Not AFAICS from what you pasted. The print time outs seem to me to be cascading fails. Highlighting what you pasted: (gdb) PASS: gdb.base/exitsignal.exp: $_exitcode is void before running continue Continuing. Program received signal SIGSEGV, Segmentation fault. 0x00003fffb7cbf808 in .raise () from target:/lib64/libc.so.6 (gdb) PASS: gdb.base/exitsignal.exp: trigger SIGSEGV continue Continuing. FAIL: gdb.base/exitsignal.exp: program terminated with SIGSEGV (timeout) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ print $_exitsignal FAIL: gdb.base/exitsignal.exp: $_exitsignal is 11 (SIGSEGV) after SIGSEGV. (timeout) print $_exitcode FAIL: gdb.base/exitsignal.exp: $_exitcode is still void after SIGSEGV (timeout) kill Program terminated with signal SIGSEGV, Segmentation fault. The program no longer exists. (gdb) print $_exitsignal $3 = 11 (gdb) print $_exitcode $4 = void That timed out waiting for the "Program terminated with signal SIGSEGV" output. Stripping the prints, we see it more clearly: Program received signal SIGSEGV, Segmentation fault. 0x00003fffb7cbf808 in .raise () from target:/lib64/libc.so.6 (gdb) PASS: gdb.base/exitsignal.exp: trigger SIGSEGV continue Continuing. FAIL: gdb.base/exitsignal.exp: program terminated with SIGSEGV (timeout) Program terminated with signal SIGSEGV, Segmentation fault. The program no longer exists. (gdb) Thanks, Pedro Alves