[PATCH 11/18] gdbserver: fix killed-outside.exp
Pedro Alves
palves@redhat.com
Thu Nov 26 17:56:00 GMT 2015
On 11/26/2015 04:51 PM, Yao Qi wrote:
> By the way, after GDBserver reported the stop GDB, does the thread
> changed to
>
> (thread->last_resume_kind == resume_stop
> && thread->last_status.kind != TARGET_WAITKIND_IGNORE)
>
> it is used in proceed_one_lwp.
>
Yes, after the stop is reported out of linux_wait, server.c does:
else
{
/* We're reporting this thread as stopped. Update its
"want-stopped" state to what the client wants, until it
gets a new resume action. */
current_thread->last_resume_kind = resume_stop;
current_thread->last_status = last_status;
}
Thanks,
Pedro Alves
More information about the Gdb-patches
mailing list