https://bugs.llvm.org/show_bug.cgi?id=37995
Bug ID: 37995
Summary: LLDB only supports GPR registers on Windows
Product: lldb
Version: 6.0
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Oh interesting, so this is an issue with cmake not just ubuntu. Thanks for
the heads up; I'll remember that when im on Darwin next.
PL
On Fri, Jun 29, 2018 at 12:07 PM Jonas Devlieghere
wrote:
> Hi Puyan,
>
> > On Jun 29, 2018, at 7:30 PM, Puyan Lotfi via lldb-dev <
> lldb-dev@lists.llvm.org> w
Hi Puyan,
> On Jun 29, 2018, at 7:30 PM, Puyan Lotfi via lldb-dev
> wrote:
>
> Just a heads up, I had run into some issues running make check-lldb. I found
> the solution to be setting:
>
> PYTHON_INCLUDE_DIRS=/usr/include/python2.7
> PYTHON_LIBRARIES=/usr/lib/python2.7/config-x86_64-linux-gn
Just a heads up, I had run into some issues running make check-lldb. I
found the solution to be setting:
PYTHON_INCLUDE_DIRS=/usr/include/python2.7
PYTHON_LIBRARIES=/usr/lib/python2.7/config-x86_64-linux-gnu/libpython2.7.so
prior to running cmake. Of course python2.7-dev needs to be installed
pri
So, on Ubuntu "sudo apt-get remove python-lldb-4.0" solved this issue.
Thanks again for the guidance.
Cheers,
Gabor
On Fri, Jun 29, 2018 at 4:10 PM Gábor Márton wrote:
> I did a search for the "HLOp" symbol and it turned out it is only used by
> the "LLVMSupport.so" lib.
> So, this did not help
I did a search for the "HLOp" symbol and it turned out it is only used by
the "LLVMSupport.so" lib.
So, this did not help, thus I dug deeper and examined the test binary
further.
`_exit` is called during the initialization of the static HLOp object
(dlopen() calls call_init() which executes the st
Hello!
lldb-mi doesn't propagate host environment variables while lldb does it:
$ cat env.c
#include
#include
int main()
{
printf("VAR = %s\n", getenv("VAR"));
return 0;
}
$ gcc env.c -o env
$ /home/kbaladurin/Downloads/llvm-x64-7.0/bin/lldb -v
lldb version 7.0.0
$ VAR=1 /home/kbaladu
https://bugs.llvm.org/show_bug.cgi?id=37986
Bug ID: 37986
Summary: Segmentation fault (core dumped) when loading core
dump (armhf on arm64)
Product: lldb
Version: 3.9
Hardware: Other
OS: Linux
St
Hi Gábor,
thanks for sending me that link line. Unfortunately, I don't see
anything immediately obvious there. (I was expecting there would be
something pulling in LLVMSupport twice, but I don't see anything like
that there).
To fix this, we need to figure out where is the second definition of
th
Hi everyone,
We’re excited to invite you to the second LLVM social in London on Thursday,
July 19.
We'll meet at Drake & Morgan (6 Pancras Square, Kings Cross, N1C 4AG) at 6:30
pm for an informal evening of LLVM-related discussions over drinks.
If you can, please help us plan and RSVP here:
h
Hi Pavel,
Thank you for the fix and for taking care of this!
So, the particular test binary is: ScriptInterpreterPythonTests .
And here is the link command:
) ninja ScriptInterpreterPythonTests -v
[1/1] : && /usr/lib/ccache/clang++ -fPIC -fvisibility-inlines-hidden
-Werror=date-time -std=c++11 -W
11 matches
Mail list logo
