> On Nov 27, 2017, at 3:50 PM, Christopher Book wrote:
>
> I have been using both a custom port-forwarding program as well as OpenSSH.
> The custom solution is a bit slower because it goes through a proxy, so the
> problem doesn't manifest. I've been trying to switch to OpenSSH which is
> f
I have been using both a custom port-forwarding program as well as
OpenSSH. The custom solution is a bit slower because it goes through a
proxy, so the problem doesn't manifest. I've been trying to switch to
OpenSSH which is fast enough to consistent hit the race condition.
I would expect other
On Mon, 27 Nov 2017 21:33:04 +0100, Christopher Book via lldb-dev wrote:
> Thoughts?
Not sure if it is applicable in this case but GDB has this feature:
https://sourceware.org/gdb/onlinedocs/gdb/Server.html#Running-gdbserver
(gdb) target remote | ssh -T hostname gdbserver - hello
When I wrote the code I was assuming that when the platform lldb-server
responds with the port that the gdb-remote would be ready to receive packets
right away, so I can see how and why this is happening. Seems like we have the
retry stuff under control when we don't get a connection right away,
Greetings, I've been using liblldb to remotely debug to a linux server with
port forwarding. To do this, I start lldb-server to with --listen
specifying a localhost port, as well as with min-gdbserver-port and
--max-gdbserver-port to specify a specific port for use by 'gdb remote'.
Both ports
I ran into the same problem with lldb 3.8 on Ubuntu 14.04. I created symlinks
to get things working right. Now I can run "lldb" and it finds lldb-server.
In /usr/bin:
0 lrwxrwxrwx 1 root root 26 Nov 17 15:22 /usr/bin/lldb ->
/usr/lib/llvm-3.8/bin/lldb*
0 lrwxrwxrwx 1 root root 24 Jul 18 11:06 /u
Hi all,
We've extended the deadline for submission to Sunday 3rd of December.
Thanks,
Kristof
2017-11-21 10:02 GMT+01:00 Kristof Beyls :
> This is just a gentle reminder that the deadline for submission is coming
> Sunday, 26th of November.
>
> Thanks,
>
> Kristof
>
> 2017-10-13 10:51 GMT+02:0
I think that's a question for your distro's (or ubuntu's) lldb package
maintainer. I think they probably have some custom patches there (if
they don't then they probably need them). If I'm not mistaken vanilla
lldb does not even support multiple lldb instalations side-by-side
(i.e., it will always
