This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug server/16879] New: support gdbserver with named pipes


https://sourceware.org/bugzilla/show_bug.cgi?id=16879

            Bug ID: 16879
           Summary: support gdbserver with named pipes
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: server
          Assignee: unassigned at sourceware dot org
          Reporter: dje at google dot com

IWBN to use gdbserver with named pipes.
That can be done today using "stdio" as the "comm port" and redirecting stdio
to/from the named pipes, except that if one is also using --multi and gdb goes
away then gdbserver gets into an infinite loop trying to read stdin which
returns EOF.  gdbserver needs to close the port and reopen it, but that doesn't
work too well for stdin (gdbserver doesn't know what to reopen as stdin, and
the close and reopen are done in different parts of the code so there's no real
guarantee that stdin won't have accidently been assigned to something else in
between).

A related PR is https://sourceware.org/bugzilla/show_bug.cgi?id=8637
but it concerns the gdb side.
[btw, named pipes are unidirectional so "target remote /foo/named-pipe" is
insufficient]
This PR concerns the gdbserver side.  gdb may be using, e.g., "target
{extended-,}remote | ssh mumble" to connect to a previously started gdbserver
that is using named pipes.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]