Hi, I'm remote debugging to linux (platform select remote-linux), and then
launching a process on the target.
> file
> process launch -w /some/dir
When I do this, the process is launched but it gets an empty list of
environment variables. I've confirmed that lldb and the gdb server both
have the
process to inherit? The env
> vars of the platform process on the remote?
>
> On Wed, Jul 5, 2017 at 8:47 AM Christopher Book via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
>
>> Hi, I'm remote debugging to linux (platform select remote-linux), and
>> the
Hi, I'm remote debugging to linux (from windows), and I'm trying to launch
a binary that already exists on both the client and target machines.
Regardless of what I do, it always wants to transfer the (very large)
executable to the remote machine and run it. Is there a way to avoid this?
I'm runn
Hi,
I posted a patch last week for a crash in gdb-remote I was seeing when
debugging a specific binary.
https://reviews.llvm.org/D36620
Is there someone that I should add to review it?
Thanks,
Chris Book
___
lldb-dev mailing list
lldb-dev@lists.llvm.o
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
> If anyone has extensive experience in port forward tech, please chime in.
>
> Short answer: not sure what the right solution is as it depends on what
> proper port forwarding etiquette is.
>
> Greg
>
>
>
>
>
> > On Nov 27, 2017, at 12:33 PM, Christopher Book via
bserver tcp://: --native-regs
Its not obvious to me from looking at the code why this is being skipped.
But I will debug further why this argument is not used in this case.
Thanks,
Chris
On Tue, Nov 28, 2017 at 5:25 AM Pavel Labath wrote:
> On 27 November 2017 at 20:33, Christopher Book via lld
I made a mistake and was not looking at the latest source. Looks like this
exact issue was already discovered and fixed:
https://reviews.llvm.org/D30255
I'm using 4.0.1, so it appears I need to upgrade.
Chris
On Wed, Nov 29, 2017 at 5:45 AM Pavel Labath wrote:
> On 28 November 2017 at 20:54,
