Hi all,
I'm going to be submitting a change shortly to enable "ninja check-lldb" on
the upstream Windows lldb buildbot. For now this is an experiment to see
how well this will go, but I would eventually like this to become
permanent. As with build breakages, the bot needs to stay green, so
Hello,
I am currently working on Bug 27687 (PrintStackTraces), so the reason
for the failure is the erroneous unwinding of the frames from the zeroth
frame. The error is not detected in AddOneMoreFrame, since it only checks
for 2 more frames, if it was checking more frames in
https://llvm.org/bugs/show_bug.cgi?id=27787
Bug ID: 27787
Summary: TopLevelExpressions fails on Android API 21-22
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Ok, I see what the problem is now. If you run llvm-config from the
build folder, it will print out the correct path for the llvm headers,
but this will not be correct for the clang headers as it points
directly to the subfolder of the source llvm checkout. In Kamil's use
case this will be fine