HI,
I am glad to see more automated testing of lldb. I think it's very
valuable as a lot of people don't have access to that platform.
On 17 May 2016 at 20:54, Zachary Turner via lldb-dev
wrote:
> Hi all,
>
> I'm going to be submitting a change shortly to enable "ninja check-lldb" on
> the upstr
https://llvm.org/bugs/show_bug.cgi?id=27803
Bug ID: 27803
Summary: Segmentation fault in lldb::SBValue::GetDescription
Product: lldb
Version: 3.8
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
On 18 May 2016 at 05:08, Pavel Labath via lldb-dev
wrote:
>
> Sounds reasonable. I'd like to add a clarifying point (2.5): If you
> have added a new test, and this test fails on some other platform AND
> there is no reason to believe that this is due to a problem in the
> test (like the python3 by
Packages/Python/lldbsuite/test/tools/lldb-mi/TestMiGdbSetShow.py, in
test_lldbmi_gdb_set_target_async_off we have this code:
self.runCmd("-gdb-set target-async off")
.
self.runCmd("-exec-run")
unexpected = [ "\*running" ] # "\*running" is async notification
https://llvm.org/bugs/show_bug.cgi?id=27806
Bug ID: 27806
Summary: thread step-over dlopen fails while running
test_step_over_load (TestLoadUnload.py)
Product: lldb
Version: unspecified
Hardware: PC
OS: Linu
