From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org, Hui Zhu <hui_zhu@mentor.com>
Subject: [commit+7.6] [testsuite patch] race: server-kill.exp: Connection reset by peer [Re: [patch+7.6] Fix 7.5 regression crashing GDB if gdbserver dies]
Date: Tue, 09 Apr 2013 16:00:00 -0000 [thread overview]
Message-ID: <20130409152826.GA25595@host2.jankratochvil.net> (raw)
In-Reply-To: <51643257.7070002@redhat.com>
On Tue, 09 Apr 2013 17:23:03 +0200, Pedro Alves wrote:
> "Triggered when there's outstanding outgoing data that has not yet been written to the other side."
>
> ncat is recv'ing the data you send it, so the window that
> could trigger is quite small.
oops, true.
Thanks for the verification.
> Looks fine to me.
Checked in:
http://sourceware.org/ml/gdb-cvs/2013-04/msg00091.html
and also for 7.6 as it is very safe patch which may easy cross-version
testing:
http://sourceware.org/ml/gdb-cvs/2013-04/msg00092.html
Thanks,
Jan
prev parent reply other threads:[~2013-04-09 15:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 19:55 [patch+7.6] Fix 7.5 regression crashing GDB if gdbserver dies Jan Kratochvil
2013-03-22 13:04 ` Pedro Alves
2013-03-22 20:29 ` Jan Kratochvil
2013-03-22 20:45 ` Pedro Alves
2013-03-22 20:55 ` Tom Tromey
2013-03-23 10:51 ` Pedro Alves
2013-03-23 16:25 ` Tom Tromey
2013-03-23 18:31 ` [commit+7.6] " Jan Kratochvil
2013-03-23 22:49 ` Pedro Alves
2013-04-02 13:41 ` Yao Qi
2013-04-02 15:20 ` Jan Kratochvil
2013-04-04 11:09 ` Yao Qi
2013-04-08 7:17 ` [testsuite patch] race: server-kill.exp: Connection reset by peer [Re: [patch+7.6] Fix 7.5 regression crashing GDB if gdbserver dies] Jan Kratochvil
2013-04-09 15:44 ` Pedro Alves
2013-04-09 16:00 ` Jan Kratochvil [this message]
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=20130409152826.GA25595@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=hui_zhu@mentor.com \
--cc=palves@redhat.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