Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Dmitry Antipov <dantipov@nvidia.com>
To: <gdb@sourceware.org>
Cc: Ryan Bissell <rbissell@nvidia.com>,
	Mikhail Filimonov	<mfilimonov@nvidia.com>
Subject: Host GDB disconnect while waiting for tracee status change
Date: Tue, 22 Aug 2017 13:23:00 -0000	[thread overview]
Message-ID: <5febbe3e-926f-78bb-db88-901b44e2e258@nvidia.com> (raw)

Hello,

Is there a feature/option/etc. to gracefully handle the situation when gdbserver
sits waiting for tracee status change and the network connection is getting lost?

AFAICS in case of Linux, linux_wait_for_event_filtered() just enters sigsuspend()
waiting for SIGCHLD and ignoring anything else, thus having no opportunity to detect
any socket status changes even if the latter are signaled with SIGIOs requested
in enable_async_notification().

Thanks in advance,
Dmitry


             reply	other threads:[~2017-08-22 13:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22 13:23 Dmitry Antipov [this message]
2017-08-23  8:18 ` Yao Qi
2017-08-23  9:37   ` Dmitry Antipov
2017-08-23 13:10     ` Pedro Alves
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=5febbe3e-926f-78bb-db88-901b44e2e258@nvidia.com \
    --to=dantipov@nvidia.com \
    --cc=gdb@sourceware.org \
    --cc=mfilimonov@nvidia.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