> On Dec 2, 2019, at 4:08 PM, Vadim Chugunov wrote:
>
> > But I don't think passing lldb's environment variables automatically when
> > running a remote process is a sensible thing to do - certainly not as the
> > default anyway. If the host and target are different OS'es and maybe
> > diff
> But I don't think passing lldb's environment variables automatically when
running a remote process is a sensible thing to do - certainly not as the
default anyway. If the host and target are different OS'es and maybe
different users, etc. lldb's environment may very well not be appropriate
for t
There's a setting (target.inherit-env) that controls whether "process launch"
passes its environment variables along with any newly set to the process in
question. Sounds like there should also be an lldb.eLaunchFlagInheritEnv that
triggers the same behavior from the SB API.
But I don't think
Hi,
I am trying to figure out the proper way of using LLDB's SBLaunchInfo class:
When I launch a process via CLI interpreter, it seems to receive all of the
environment variables inherited from shell, plus the ones I set via
`target.env-vars`:
(lldb) file /usr/bin/env
Current executable set to '/u
