[lldb-dev] environment vars not passed through to linux targets
Pavel Labath via lldb-dev
lldb-dev at lists.llvm.org
Thu Jul 6 02:46:02 PDT 2017
Yes, that looks like a bug. Inheriting the target environment in the
default case sounds like a good thing to do. I had a feeling it used
to work at some point, but I could be wrong...
On 6 July 2017 at 05:04, Christopher Book via lldb-dev
<lldb-dev at lists.llvm.org> wrote:
> Yes, exactly. So things like LD_LIBRARY_PATH, PATH and others that are set
> based on the target linux env. The client doesn't have this information
> available to manually set them all.
> On Wed, Jul 5, 2017 at 11:44 PM Stephane Sezer <sas at cd80.net> wrote:
>> Which set of env vars did you want the child 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 at lists.llvm.org> wrote:
>>> Hi, I'm remote debugging to linux (platform select remote-linux), and
>>> then launching a process on the target.
>>> > file <my binary>
>>> > 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 vars, but not the target process.
>>> I can manually pass environment variables to the target using the
>>> '--environment' flag, and this works. But in general I need these to be
>>> Based on online comments about this working on mac, this appears to be a
>>> linux-specific bug? Is this expected or known?
>>> Chris Book
>>> lldb-dev mailing list
>>> lldb-dev at lists.llvm.org
>> Stephane Sezer
> lldb-dev mailing list
> lldb-dev at lists.llvm.org
More information about the lldb-dev