From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 91307 invoked by alias); 17 Oct 2017 14:00:53 -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 91276 invoked by uid 89); 17 Oct 2017 14:00:53 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy= X-HELO: mx0a-001b2d01.pphosted.com Received: from mx0a-001b2d01.pphosted.com (HELO mx0a-001b2d01.pphosted.com) (148.163.156.1) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 17 Oct 2017 14:00:46 +0000 Received: from pps.filterd (m0098394.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v9HE01PG029470 for ; Tue, 17 Oct 2017 10:00:45 -0400 Received: from e06smtp15.uk.ibm.com (e06smtp15.uk.ibm.com [195.75.94.111]) by mx0a-001b2d01.pphosted.com with ESMTP id 2dnjrw1xy8-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Tue, 17 Oct 2017 10:00:43 -0400 Received: from localhost by e06smtp15.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 17 Oct 2017 15:00:35 +0100 Received: from b06cxnps4076.portsmouth.uk.ibm.com (9.149.109.198) by e06smtp15.uk.ibm.com (192.168.101.145) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Tue, 17 Oct 2017 15:00:33 +0100 Received: from d06av24.portsmouth.uk.ibm.com (d06av24.portsmouth.uk.ibm.com [9.149.105.60]) by b06cxnps4076.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v9HE0WWQ17105116; Tue, 17 Oct 2017 14:00:32 GMT Received: from d06av24.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id A124442041; Tue, 17 Oct 2017 14:56:06 +0100 (BST) Received: from d06av24.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 852434203F; Tue, 17 Oct 2017 14:56:06 +0100 (BST) Received: from oc3748833570.ibm.com (unknown [9.167.243.191]) by d06av24.portsmouth.uk.ibm.com (Postfix) with ESMTP; Tue, 17 Oct 2017 14:56:06 +0100 (BST) Received: by oc3748833570.ibm.com (Postfix, from userid 1000) id 2D8AAD807C2; Tue, 17 Oct 2017 16:00:32 +0200 (CEST) Subject: Sporadic failures of selftest tests To: gdb-patches@sourceware.org Date: Tue, 17 Oct 2017 14:00:00 -0000 From: "Ulrich Weigand" Cc: palves@redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 x-cbid: 17101714-0020-0000-0000-000003C1A963 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17101714-0021-0000-0000-000042562CBC Message-Id: <20171017140032.2D8AAD807C2@oc3748833570.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-10-17_10:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=4 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1710170196 X-SW-Source: 2017-10/txt/msg00522.txt.bz2 Hello, I'm now seeing sporadic failures of some of the self-test test cases running natively on x64_86. A failing case looks like: (gdb) break captured_command_loop Breakpoint 1 at 0x7117b0: file ../../binutils-gdb/gdb/main.c, line 324. (gdb) PASS: gdb.gdb/complaints.exp: breakpoint in captured_command_loop run -nw -nx -data-directory /home/uweigand/fsf/binutils-gdb-build/gdb/testsuite/../data-directory Starting program: /home/uweigand/fsf/binutils-gdb-build/gdb/testsuite/outputs/gdb.gdb/complaints/xgdb -nw -nx -data-directory /home/uweigand/fsf/binutils-gdb-build/gdb/testsuite/../data-directory [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". GNU gdb (GDB) 8.0.50.20171017-git Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". (gdb) FAIL: gdb.gdb/complaints.exp: run until breakpoint at captured_command_loop WARNING: Couldn't test self while the good case looks instead like: (gdb) break captured_command_loop Breakpoint 1 at 0x7117b0: file ../../binutils-gdb/gdb/main.c, line 324. (gdb) PASS: gdb.gdb/complaints.exp: breakpoint in captured_command_loop run -nw -nx -data-directory /home/uweigand/fsf/binutils-gdb-build/gdb/testsuite/../data-directory Starting program: /home/uweigand/fsf/binutils-gdb-build/gdb/testsuite/outputs/gdb.gdb/complaints/xgdb -nw -nx -data-directory /home/uweigand/fsf/binutils-gdb-build/gdb/testsuite/../data-directory [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". GNU gdb (GDB) 8.0.50.20171017-git Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word". (gdb) Breakpoint 1, captured_main (data=0x7fffffffd2e0) at ../../binutils-gdb/gdb/main.c:1147 1147 captured_command_loop (); (gdb) XFAIL: gdb.gdb/complaints.exp: run until breakpoint at captured_command_loop (line numbers scrambled?) Just from reading the logs this looks like the gdb_test_multiple in selftest_setup gets the GDB prompt from the inferior GDB and assumes it comes from the outer GDB. Depending on the exact timing, it might see this before the breakpoint message, and fall into the failure case of the gdb_test_multiple ... Pedro, I'm not sure if this may have anything to do with your recent testsuite changes, but I didn't see any other obvious candidates in the logs either :-) Have you see this issue before? How is this supposed to work in the first place? Is there anything that would allow the testsuite to distinguish the gdb prompts emitted by the two GDBs? Bye, Ulrich -- Dr. Ulrich Weigand GNU/Linux compilers and toolchain Ulrich.Weigand@de.ibm.com