This is the mail archive of the
mailing list for the GDB project.
RE: [PATCH 13/17] btrace: non-stop
- From: "Metzger, Markus T" <markus dot t dot metzger at intel dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Thu, 10 Sep 2015 07:47:42 +0000
- Subject: RE: [PATCH 13/17] btrace: non-stop
- Authentication-results: sourceware.org; auth=none
- References: <1441794909-32718-1-git-send-email-markus dot t dot metzger at intel dot com> <1441794909-32718-14-git-send-email-markus dot t dot metzger at intel dot com> <55F01DEC dot 4030209 at redhat dot com> <A78C989F6D9628469189715575E55B23331AB7A1 at IRSMSX104 dot ger dot corp dot intel dot com> <55F03852 dot 7030200 at redhat dot com> <A78C989F6D9628469189715575E55B23331AB873 at IRSMSX104 dot ger dot corp dot intel dot com> <55F04765 dot 9020206 at redhat dot com>
> -----Original Message-----
> From: email@example.com [mailto:gdb-patches-
> firstname.lastname@example.org] On Behalf Of Pedro Alves
> Sent: Wednesday, September 9, 2015 4:51 PM
> To: Metzger, Markus T
> Cc: email@example.com
> Subject: Re: [PATCH 13/17] btrace: non-stop
> On 09/09/2015 03:08 PM, Metzger, Markus T wrote:
> >>> Wouldn't the 1st or 2nd pattern skip any $gdb_prompt before the
> >> Yes. Is that a problem? Don't we always get another prompt after that
> >> error?
> > No, we don't. We have a single prompt that appears somewhere in the
> > (gdb) thread apply all continue
> That seems to be root of the problem. That'll do a synchronous
> continue on each thread, one by one. I think that what you want
> is instead:
> (gdb) thread apply all continue&
> And that way you get a single prompt before any breakpoint is hit.
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.
I changed the test, removed the "Cannot execute ..." check, and pushed the
series into users/mmetzger/btrace-non-stop.
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