From: Pedro Alves <palves@redhat.com>
To: lgustavo@codesourcery.com
Cc: "'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>
Subject: Re: [PATCH, remote] Handle 'k' packet errors gracefully
Date: Mon, 22 Apr 2013 21:06:00 -0000 [thread overview]
Message-ID: <51754F1D.9000300@redhat.com> (raw)
In-Reply-To: <517549FC.5070606@codesourcery.com>
Hi Luis,
On 04/22/2013 03:32 PM, Luis Machado wrote:
> This is not a real problem with gdbserver, but other types of remote targets (other stubs, QEMU etc) may cut the connection abruptly since they are not required to reply to a 'k' (Kill) packet sent from GDB.
>
> The following patch addresses any issues arising from such scenario, which leads to a GDB internal error due to an attempt to pop the target more than once. With the patch, this failure is handled gracefully.
Hard to say without at least seeing the backtrace, but this may no longer
be applicable due to changes in this area since (some quite recent).
> As the ChangeLog suggests, i'm sending this on behalf of its original authors.
This needs to be updated to take the new TARGET_CLOSE_ERROR
exception into account.
Thanks,
--
Pedro Alves
next prev parent reply other threads:[~2013-04-22 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 19:03 Luis Machado
2013-04-22 21:06 ` Pedro Alves [this message]
[not found] ` <alpine.DEB.1.10.1311301416410.21686@tp.orcam.me.uk>
2013-12-02 10:57 ` 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=51754F1D.9000300@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.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