If it's on Mac OS X 10.11, I saw this the other day. e.g.
sh-3.2$ cat a.c
#include
#include
int main()
{
printf("%s\n", getenv("DYLD_LIBRARY_PATH"));
}
sh-3.2$ clang a.c
sh-3.2$ lldb -x a.out
(lldb) target create "a.out"
Current executable set to 'a.out' (x86_64).
(lldb) pro lau -v DYLD_L
I am surprised that this doesn't work as we make an effort to pass the current
environment down to any processes that you spawn by default (at least on MacOSX
we do), but the solution is easy: use the --environment variable with the
"process launch" command:
(lldb) process launch --environment
Hi.
I'm fairly new to lldb, been using gdb most of my life.
I'm currently hacking on a small library which I'm building without
installing. Usually I'm running tests for the library also without
installing, but rather using DYLD_LIBRARY_PATH in this manner:
DYLD_LIBRARY_PATH= mytestbinary
On lin
