rdhindsa added a comment.
With this patch, it looks like the test added in this patch fails for
lldb-arm-ubuntu:
https://lab.llvm.org/buildbot/#/builders/17/builds/10498
Everything passes on these buildbots: lldb-aarch64-ubuntu,
lldb-x64-windows-ninja, lldb-x86_64-debian.
The test logic checks for breakpoint for main as well as for shared library
load. It is able to extract that information using thread.GetFrameAtIndex(0).
However, when it gets the signal, it is not able to extract the back trace and
hence fails with the following error:
ERROR: test (TestDyldLaunchLinux.TestLinux64LaunchingViaDynamicLoader)
Traceback (most recent call last):
File
"/home/tcwg-buildslave/worker/lldb-arm-ubuntu/llvm-project/lldb/test/API/functionalities/dyld-launch-linux/TestDyldLaunchLinux.py",
line 57, in test
self.assertIn("raise", thread.GetFrameAtIndex(0).GetDisplayFunctionName())
File
"/home/tcwg-buildslave/worker/lldb-arm-ubuntu/llvm-project/lldb/third_party/Python/module/unittest2/unittest2/case.py",
line 884, in assertIn
if member not in container:
TypeError: argument of type 'NoneType' is not iterable
Config=arm-/home/tcwg-buildslave/worker/lldb-arm-ubuntu/build/bin/clang
@DavidSpickett, @zatrazz: If possible, could you please take a look. Is this
expected behavior and test should be marked as unsupported for arm, or am I
missing something here?
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D108061/new/
https://reviews.llvm.org/D108061
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
