From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 67744 invoked by alias); 10 Sep 2015 11:37:23 -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 67573 invoked by uid 89); 10 Sep 2015 11:37:22 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mga02.intel.com Received: from mga02.intel.com (HELO mga02.intel.com) (134.134.136.20) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 10 Sep 2015 11:37:21 +0000 Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP; 10 Sep 2015 04:37:18 -0700 X-ExtLoop1: 1 Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by orsmga001.jf.intel.com with ESMTP; 10 Sep 2015 04:37:17 -0700 Received: from irsmsx104.ger.corp.intel.com ([169.254.5.201]) by IRSMSX153.ger.corp.intel.com ([169.254.9.13]) with mapi id 14.03.0224.002; Thu, 10 Sep 2015 12:37:16 +0100 From: "Metzger, Markus T" To: Pedro Alves CC: "gdb-patches@sourceware.org" Subject: RE: [PATCH 13/17] btrace: non-stop Date: Thu, 10 Sep 2015 11:37:00 -0000 Message-ID: References: <1441794909-32718-1-git-send-email-markus.t.metzger@intel.com> <1441794909-32718-14-git-send-email-markus.t.metzger@intel.com> <55F01DEC.4030209@redhat.com> <55F03852.7030200@redhat.com> <55F04765.9020206@redhat.com> <55F163DD.4050809@redhat.com> <55F16A58.8070403@redhat.com> In-Reply-To: <55F16A58.8070403@redhat.com> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2015-09/txt/msg00156.txt.bz2 > -----Original Message----- > From: Pedro Alves [mailto:palves@redhat.com] > Sent: Thursday, September 10, 2015 1:33 PM > To: Metzger, Markus T > Cc: gdb-patches@sourceware.org > Subject: Re: [PATCH 13/17] btrace: non-stop >=20 > On 09/10/2015 12:19 PM, Metzger, Markus T wrote: > >> -----Original Message----- > >> From: Pedro Alves [mailto:palves@redhat.com] > >> Sent: Thursday, September 10, 2015 1:05 PM > >> To: Metzger, Markus T > >> Cc: gdb-patches@sourceware.org > >> Subject: Re: [PATCH 13/17] btrace: non-stop > >> > >> On 09/10/2015 08:47 AM, Metzger, Markus T wrote: > >> > >>> That seems to be the case. I'm still getting the error I'm checking = for > before > >>> the prompt, though, and my test will run into a timeout. > >>> > >>> thread apply all reverse-stepi 4 & > >>> > >>> Thread 2 (Thread 0x7ffff74fb700 (LWP 70895)): > >>> > >>> Thread 1 (Thread 0x7ffff7fcc740 (LWP 70891)): > >>> Cannot execute this command while the selected thread is running. > >>> (gdb) PASS: gdb.btrace/non-stop.exp: reverse-step: all: thread apply > >> all reverse-stepi 4: prompt > >>> 0x0000000000400671 28 for (; i < 10; ++i) global +=3D i;= /* loop */ > >>> PASS: gdb.btrace/non-stop.exp: reverse-step: all: thread apply all > >> reverse-stepi 4: thread 0 > >>> FAIL: gdb.btrace/non-stop.exp: reverse-step: all: thread apply all > >> reverse-stepi 4: thread 1 (timeout) > >>> > >>> A failing run might take a bit longer, but that should be it. > >> > >> Odd. I'm running the test now for over 20 minutes, and it doesn't ever > fail. > >> Before I ran it against gdbserver for 10 minutes, never failed. > >> This is with an i7-2620M; I hacked linux-btrace.c:intel_supports_bts to > >> enable btrace. > > > > I reverted one of the patches to trigger the error. I wanted to see if > > the test catches it. The full series should run without error, of cour= se. > > > > This was meant to demonstrate that the error message precedes the > > prompt. >=20 > Ah, I had totally misunderstood it! I thought you were saying that a > failing run took a bit long to trigger, so I left it running for a > while. In fact, I still had it running. :-) I meant that when a test fails, we are now waiting for the timeout. Before, we caught the error message. So running the test might take longer if there are fails. I forgot to mention that you need to revert one of the preceding patches to trigger a fail;-) Regards, Markus. Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Prof. Dr. Hermann Eul Chairperson of the Supervisory Board: Tiffany Doon Silva Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928