This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Move threads out of jumppad without single step
- From: Simon Marchi <simon dot marchi at ericsson dot com>
- To: Pedro Alves <palves at redhat dot com>, Yao Qi <qiyaoltc at gmail dot com>, <gdb-patches at sourceware dot org>
- Date: Mon, 30 Nov 2015 14:04:08 -0500
- Subject: Re: Move threads out of jumppad without single step
- Authentication-results: sourceware.org; auth=none
- References: <86zixzvhj1 dot fsf at gmail dot com> <565C6043 dot 4040106 at redhat dot com>
On 15-11-30 09:42 AM, Pedro Alves wrote:
> So I assume it's much simpler to just run to [1] as well, and then issue
> a normal software single-step when you get there.
>
> Also, not sure, but it's possible the stabilize threads machinery may
> need work to handle the "wrong threads" hitting that "out of jump pad"
> single-step breakpoint for another thread, and not have them start
> a new start over, but instead have them be locked immediately.
To be clear, do you mean, when single stepping the last jump pad instruction,
the jump that goes back to the regular code? When putting a breakpoint on the
next pc of that instruction, it means putting a breakpoint in the regular code.
However, when doing a single step in gdbserver, aren't all other threads stopped?