From: Tom Tromey <tom@tromey.com>
To: John Darrington <john@darrington.wattle.id.au>
Cc: gdb-patches@sourceware.org
Subject: Re: Remote debugging over local domain sockets?
Date: Wed, 29 Aug 2018 15:17:00 -0000 [thread overview]
Message-ID: <878t4p5hjn.fsf@tromey.com> (raw)
In-Reply-To: <20180829070540.gv25gh2zph3dfced@jocasta.intra> (John Darrington's message of "Wed, 29 Aug 2018 09:05:40 +0200")
>>>>> "John" == John Darrington <john@darrington.wattle.id.au> writes:
John> So far as I'm aware, it's not possible to run a remote target over
John> a local domain (AF_UNIX) socket.
John> Would you accept a patch which changes the behaviour of "target
John> remote /foo/bar" such that if /foo/bar is a socket, gdb will
John> connect to that socket instead of trying to open it as a device?
How about stat'ing the path and doing the right thing depending on
whether it is a device or a socket?
Alternatively, how about new syntax instead? "target remote /path" has meant
to open a serial device since forever. However there's also syntax like
"target remote udp:host:port". So maybe "target remote socket:/path"?
Tom
next prev parent reply other threads:[~2018-08-29 15:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 7:05 John Darrington
2018-08-29 15:17 ` Tom Tromey [this message]
2018-08-29 15:28 ` John Darrington
2018-08-29 15:39 ` Tom Tromey
2018-08-31 10:18 ` [PATCH] Allow remote debugging over a local domain socket John Darrington
2018-08-31 14:59 ` Eli Zaretskii
2018-08-31 15:10 ` John Darrington
2018-08-31 17:50 ` Eli Zaretskii
2018-08-31 15:10 ` Tom Tromey
2018-08-31 15:12 ` John Darrington
2018-08-31 16:01 ` Pedro Alves
2018-08-31 16:40 ` John Darrington
2018-09-03 13:19 ` Pedro Alves
2018-09-03 18:49 ` John Darrington
2018-10-01 19:45 ` Pedro Alves
2018-10-02 10:16 ` John Darrington
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=878t4p5hjn.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=john@darrington.wattle.id.au \
/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