From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 41961 invoked by alias); 10 Sep 2015 11:32:45 -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 41948 invoked by uid 89); 10 Sep 2015 11:32:44 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_PASS,T_RP_MATCHES_RCVD autolearn=no 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; Thu, 10 Sep 2015 11:32:43 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (Postfix) with ESMTPS id 93DB9C0B9885; Thu, 10 Sep 2015 11:32:42 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t8ABWfCj026217; Thu, 10 Sep 2015 07:32:41 -0400 Message-ID: <55F16A58.8070403@redhat.com> Date: Thu, 10 Sep 2015 11:32: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: "Metzger, Markus T" CC: "gdb-patches@sourceware.org" Subject: Re: [PATCH 13/17] btrace: non-stop 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> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2015-09/txt/msg00154.txt.bz2 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 += 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 course. > > This was meant to demonstrate that the error message precedes the > prompt. 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. :-) Thanks, Pedro Alves