From: Yao Qi <qiyaoltc@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
t@adacore.com, Don Breazeal <donb@codesourcery.com>,
Pedro Alves <palves@redhat.com>, Yao Qi <yao.qi@arm.com>,
Antoine Tremblay <antoine.tremblay@ericsson.com>
Subject: Re: GDB 7.12 release - 2016-09-21 update?
Date: Thu, 22 Sep 2016 10:40:00 -0000 [thread overview]
Message-ID: <CAH=s-PMCfM6on4jbkRnrHfU5FSXe4zVsWoFzP8PEtQfgqbh4Vg@mail.gmail.com> (raw)
In-Reply-To: <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 (齐尧)
next prev parent reply other threads:[~2016-09-22 10:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 17:17 Joel Brobecker
2016-09-21 17:52 ` Simon Marchi
2016-10-03 21:10 ` Simon Marchi
2016-09-21 18:30 ` Don Breazeal
2016-09-22 10:40 ` Yao Qi [this message]
2016-09-27 18:16 ` Jan Kratochvil
2016-10-06 12:12 ` Pedro Alves
2016-10-06 14:51 ` Pedro Alves
2016-10-06 16:33 ` Maciej W. Rozycki
2016-10-06 16:41 ` Joel Brobecker
2016-10-07 15:41 ` Pedro Alves
2016-10-07 16:47 ` Joel Brobecker
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='CAH=s-PMCfM6on4jbkRnrHfU5FSXe4zVsWoFzP8PEtQfgqbh4Vg@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=antoine.tremblay@ericsson.com \
--cc=brobecker@adacore.com \
--cc=donb@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=t@adacore.com \
--cc=yao.qi@arm.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