This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Host GDB disconnect while waiting for tracee status change

From: Dmitry Antipov <dantipov at nvidia dot com>
To: Pedro Alves <palves at redhat dot com>, Yao Qi <qiyaoltc at gmail dot com>
Cc: <gdb at sourceware dot org>, Ryan Bissell <rbissell at nvidia dot com>, "Mikhail Filimonov" <mfilimonov at nvidia dot com>
Date: Wed, 23 Aug 2017 16:55:03 +0300
Subject: Re: Host GDB disconnect while waiting for tracee status change
Authentication-results: sourceware.org; auth=none
References: <5febbe3e-926f-78bb-db88-901b44e2e258@nvidia.com> <867exusnn8.fsf@gmail.com> <98251d5d-646b-296c-acf6-43ec4accd4e0@nvidia.com> <ef18541c-c0ff-26c5-b8a4-b568fa15b94a@redhat.com>

On 08/23/2017 04:10 PM, Pedro Alves wrote:

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. So, is it mandatory to use non-stop mode if I want to be able to
restart gdb without loosing the debugging session controlled by gdbserver?

Dmitry

Follow-Ups:
- Re: Host GDB disconnect while waiting for tracee status change
  - From: Pedro Alves

References:
- Host GDB disconnect while waiting for tracee status change
  - From: Dmitry Antipov
- Re: Host GDB disconnect while waiting for tracee status change
  - From: Yao Qi
- Re: Host GDB disconnect while waiting for tracee status change
  - From: Dmitry Antipov
- Re: Host GDB disconnect while waiting for tracee status change
  - From: Pedro Alves

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]