From: Pedro Alves <palves@redhat.com>
To: Dmitry Antipov <dantipov@nvidia.com>, Yao Qi <qiyaoltc@gmail.com>
Cc: gdb@sourceware.org, Ryan Bissell <rbissell@nvidia.com>,
Mikhail Filimonov <mfilimonov@nvidia.com>
Subject: Re: Host GDB disconnect while waiting for tracee status change
Date: Wed, 23 Aug 2017 13:10:00 -0000 [thread overview]
Message-ID: <ef18541c-c0ff-26c5-b8a4-b568fa15b94a@redhat.com> (raw)
In-Reply-To: <98251d5d-646b-296c-acf6-43ec4accd4e0@nvidia.com>
On 08/23/2017 10:37 AM, Dmitry Antipov wrote:
> Immediately after killing gdb, gdbserver reports:
> ...
> client connection closed
> my_waitpid (-1, 0x40000001)
> my_waitpid (-1, 0x40000001): status(ffffffff), 0
> LWFE: waitpid(-1, ...) returned 0, ERRNO-OK
> leader_pid=21352, leader_lp!=NULL=1, num_lwps=1, zombie=0
> sigsuspend'ing
> ...
>
> Next, a new instance of gdb is unable to reconnect:
...
> And it seems that there is no similar issue in a non-stop mode. For
> example:
...
> This way, a new instance of gdb can reconnect:
Right, because in non-stop mode, linux-low.c doesn't
usually block inside mywait....sigsuspend. See server.c:resume.
In non-stop mode, gdbserver waits for both socket events and
target events at the same time in the event loop. The
non-stop variant of the RSP is asynchronous.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-08-23 13:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 13:23 Dmitry Antipov
2017-08-23 8:18 ` Yao Qi
2017-08-23 9:37 ` Dmitry Antipov
2017-08-23 13:10 ` Pedro Alves [this message]
2017-08-23 13:56 ` Dmitry Antipov
2017-08-23 15:01 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ef18541c-c0ff-26c5-b8a4-b568fa15b94a@redhat.com \
--to=palves@redhat.com \
--cc=dantipov@nvidia.com \
--cc=gdb@sourceware.org \
--cc=mfilimonov@nvidia.com \
--cc=qiyaoltc@gmail.com \
--cc=rbissell@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox