This is the mail archive of the
mailing list for the GDB project.
Re: [PATCH 13/17] btrace: non-stop
- From: Pedro Alves <palves at redhat dot com>
- To: "Metzger, Markus T" <markus dot t dot metzger at intel dot com>
- Cc: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Wed, 09 Sep 2015 15:51:17 +0100
- 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>
On 09/09/2015 03:08 PM, Metzger, Markus T wrote:
>>> Wouldn't the 1st or 2nd pattern skip any $gdb_prompt before the pattern?
>> Yes. Is that a problem? Don't we always get another prompt after that
> No, we don't. We have a single prompt that appears somewhere in the output.
> (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
(gdb) thread apply all continue&
And that way you get a single prompt before any breakpoint is hit.
> OK. This is temporary. I have not followed the discussion. Can I force-push
> and remove such a user branch?
I don't think you can force-push today, but you can delete branches, so the
usual workaround of doing delete+push to emulate force-push works fine.
(Myself, I only use the user branches in the master repo to hand off series for
review and testing convenience, and do development / backup elsewhere.)