It looks like lots of options to debugserver were added without also adding
them to the --help output. Probably because there are so few clients they
already know the options (the same person added & used them...) But if you
look at the actual options in debugserver.cpp, you will see:
{"unix-socket", required_argument, NULL,
'u'}, // If we need to handshake with our parent process, an option will be
// passed down that specifies a unix socket name to use
{"fd", required_argument, NULL,
'2'}, // A file descriptor was passed to this process when spawned that
// is already open and ready for communication
{"named-pipe", required_argument, NULL, 'P'},
{"reverse-connect", no_argument, NULL, 'R'},
Will one of those serve your purpose?
Jim
> On Aug 9, 2018, at 6:20 AM, Alexander Polyakov via Phabricator
> <revi...@reviews.llvm.org> wrote:
>
> apolyakov added a subscriber: t.p.northover.
> apolyakov added a comment.
>
> It seems that `target-select-so-path.test` hangs on macOS. Thanks to
> @t.p.northover for noting this.
>
> The debugserver doesn't have `--pipe` option, so on macOS it fails to start
> and the test hangs waiting for output from debugserver. Is there any
> alternative for `--pipe` option to let the debugserver choose a tcp port
> itself? I took a quick look at debugserver's sources and didn't find it.
>
>
> Repository:
> rL LLVM
>
> https://reviews.llvm.org/D49739
>
>
>
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
