This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: GDB 7.12 release - 2016-09-21 update?
- From: Yao Qi <qiyaoltc at gmail dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>, t at adacore dot com, Don Breazeal <donb at codesourcery dot com>, Pedro Alves <palves at redhat dot com>, Yao Qi <yao dot qi at arm dot com>, Antoine Tremblay <antoine dot tremblay at ericsson dot com>
- Date: Thu, 22 Sep 2016 11:28:52 +0100
- Subject: Re: GDB 7.12 release - 2016-09-21 update?
- Authentication-results: sourceware.org; auth=none
- References: <20160921171639.GB3842@adacore.com>
On Wed, Sep 21, 2016 at 6:16 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>
> PR 20627: GDBserver can not be closed
>
> Assigned to: *** UNASSIGNED ***
> Status: ???
>
> Not sure if this is a regression or not, and whether it is
> actually critical for 7.12. If there is no data loss, perhaps
> we can just document the workaround.
>
> Yao?
>
There is no such problem on 7.11.1.
Since the GDBserver can not be closed, GDB can not quit until it gets
packet error. (I start GDB in one window and start GDBserver in the
other.)
(gdb) quit
A debugging session is active.
Inferior 1 [process 14736] will be killed.
Quit anyway? (y or n) y
Ignoring packet error, continuing...
In my real remote testing, GDB can quit and GDBserver process leaves
on the target machine. There are a lot of GDBserver processes left after
running GDB testsuite.
I am looking into this bug...
--
Yao (齐尧)