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: Yao Qi <qiyaoltc at gmail dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: Yao Qi <qiyaoltc at gmail dot com>, gdb-patches at sourceware dot org, simon dot marchi at ericsson dot com
- Date: Tue, 01 Dec 2015 11:36:26 +0000
- 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>
Pedro Alves <palves@redhat.com> writes:
> You may be able to handle this by retrieving state from the saved registers
> buffer in the jump pad, similar to how gdb_collect cooks up a regcache, though
> unlike gdb_collect, you'll have to handle the case of the thread stopping
> midway through that register saving too (some registers already saved, some not
> yet).
Compute the next PCs on the basis of cooked up regcache from stack is
what I intended, but I didn't consider the case thread is stopped in the
middle way of register saving.
>
> 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.
Then, looks we have to use software single step.
--
Yao (éå)