This is the mail archive of the
mailing list for the GDB project.
Re: About remote target AF_UNIX socket addition ?
- From: Pedro Alves <pedro at codesourcery dot com>
- To: gdb at sourceware dot org
- Cc: Philippe Waille <Philippe dot Waille at imag dot fr>
- Date: Fri, 27 Mar 2009 14:57:02 +0000
- Subject: Re: About remote target AF_UNIX socket addition ?
- References: <20090327143915.GA18690@otto.imag.fr>
On Friday 27 March 2009 14:39:15, Philippe Waille wrote:
> The target command allows remote stub access through TCP sockets.
> Could it be extended to local unix domain (AF_UNIX) sockets as well ?
> gdb> target remote | some_stub_target /* existing */
> gdb> target remote tcp:host:ip_port_number /* existing */
> gdb> target remote unix:local_filesystem_port_name /* suggested */
> Typical usage :
> + a set of users perform debugging on a shared POSIX server
> + each user execute gdb and a target (a processor simulator, for instance),
> both on the local server
> + the target stub does not offer the remote pipe connection method,
> but allows socket connections.
> Each user has to be allocated a private port name in order to bind its
> gdb with its target. It is easier to do in the AF_UNIX local
> filesystem naming space than in the gloabl TCP/IP port numbering space.
I'm not objecting, but, my knee jerk reaction would be to implement a
netcat/socat-like stub that does stdio <-> unix socket forwarding, so
target remote | mypipe_to_socket_gateway