This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[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]
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: gdb-patches at sourceware dot org, Hui Zhu <hui_zhu at mentor dot com>
- Date: Tue, 9 Apr 2013 17:28:26 +0200
- 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]
- References: <20130315195359 dot GA19841 at host2 dot jankratochvil dot net> <514C50EF dot 6030202 at redhat dot com> <20130322191841 dot GA29259 at host2 dot jankratochvil dot net> <20130406192632 dot GA8832 at host2 dot jankratochvil dot net> <51643257 dot 7070002 at redhat dot 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