This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 11/18] gdbserver: fix killed-outside.exp
- From: Pedro Alves <palves at redhat dot com>
- To: Yao Qi <qiyaoltc at gmail dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 26 Nov 2015 17:56:18 +0000
- Subject: Re: [PATCH 11/18] gdbserver: fix killed-outside.exp
- Authentication-results: sourceware.org; auth=none
- References: <1444836486-25679-1-git-send-email-palves at redhat dot com> <1444836486-25679-12-git-send-email-palves at redhat dot com> <86ziz4zlof dot fsf at gmail dot com> <5655CE81 dot 3090603 at redhat dot com> <86fuzswvov dot fsf at gmail dot com>
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