From: Gabriel Corona <gabriel.corona@enst-bretagne.fr>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Make gdbserver connect to SOCK_STREAM sockets
Date: Tue, 05 May 2015 20:19:00 -0000 [thread overview]
Message-ID: <20150505201918.GA12154@marvin> (raw)
In-Reply-To: <1430856897-12051-2-git-send-email-gabriel.corona@enst-bretagne.fr>
This second patch may not be that useful because gdbserver is launched
first and starts communicating immediately without waiting for a
remote side to connect to the socket. If the other side is launched
too late, gdbserver has already timed-out and the communication fails
with:
> Remote debugging using |socat STDIO UNIX-LISTEN:a.sock
> Ignoring packet error, continuing...
> warning: unrecognized item "timeout" in "qSupported" response
> Ignoring packet error, continuing..
--
Gabriel
prev parent reply other threads:[~2015-05-05 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 20:15 [PATCH 1/2] Use a shell command as a socket for gdbserver Gabriel Corona
2015-05-05 20:16 ` [PATCH 2/2] Make gdbserver connect to SOCK_STREAM sockets Gabriel Corona
2015-05-05 20:19 ` Gabriel Corona [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=20150505201918.GA12154@marvin \
--to=gabriel.corona@enst-bretagne.fr \
--cc=gdb-patches@sourceware.org \
/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