Hi Adrian,
Thanks very much for sharing your results.
Carlos
On Tue, Sep 26, 2017 at 4:31 PM, Adrian McCarthy
wrote:
> I haven't spent too much time in LLDB lately. The number of failures you
> see seems a little high. On Windows 7, I get:
>
> ===
> Test Result Summary
>
Hi Adrian,
As you are working on the above Windows issue, I am assuming you are
running LLDB on Windows.
I have managed to build LLDB on Windows 10, after getting the correct
dependencies.
But from the LLDB home page, it seems that LLDB is only built and no tests
are run:
- LLDB Windows Serve
Hi,
I been trying to run the LLDB test suite on Windows (check-lldb).
The LLDB used was build with VS2015 and ninja.
When I try to run an specific test, using the commands:
cd D:\LLVM\llvm\tools\lldb\test
python dotest.py --executable "D:\LLVM\build-ninja-lldb\bin\lldb.exe" -p
TestInlineSteppin
xe ..\llvm
>
> You can add the following options if needed:
>
> -DLLDB_TEST_DEBUG_TEST_CRASHES=1
> -DLLDB_RELOCATABLE_PYTHON=1
> -DLLDB_TEST_COMPILER=
>
> My next tasks are:
>
> try: check-all, check_lldb configurations.
>
> I will post my findings.
>
> Ho
t; -std=c++11 -g -O0 -fno-builtin -m32 --driver-mode=g++ calling.cpp" and then
>> observe that caller_trivial_2 have a DW_AT_low_pc = 0x8048790 and the
>> inlined inline_trivial_1 inside it have a DW_AT_low_pc = 0x8048793 but the
>> first line entry after "Set prologue_
48793 but the
> first line entry after "Set prologue_end to true" is at 0x8048796 while
> previously it was at 0x8048793.
>
> Tamas
>
> On Thu, Sep 14, 2017 at 9:59 AM Carlos Alberto Enciso via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
>
>> Hi,
>&
Hi,
I have been working on a compiler issue, where instructions associated to
the function prolog are assigned line information, causing the debugger to
show incorrectly the beginning of the function body.
For a full description, please see:
https://reviews.llvm.org/D37625
https://reviews.llvm.o
