Open Michael137 opened 5 days ago
@llvm/issue-subscribers-lldb
Author: Michael Buch (Michael137)
@ashgti mind taking a look?
Full build/test log attached:
Since 'details' is missing, it looks like we're not getting the SBThread.GetCurrentException
result here:
https://github.com/llvm/llvm-project/blob/main/lldb/tools/lldb-dap/lldb-dap.cpp#L1233-L1234
I'll see if I can reproduce this running locally.
I've run this multiple times locally on a few commits today (my current main is 95b680e4c353d479fbfb96adb39696042c005e99) but I haven't reproduced this locally, I'm not 100% sure why we're missing the c++ exception in some cases.
I'll keep an eye on https://ci.swift.org/job/llvm.org/view/LLDB/job/as-lldb-cmake/ and see if I can figure out anything from the CI logs. We might need to add some additional logging or something since I'm not currently reproducing this issue.
For reference, there is another test that uses this API: https://github.com/llvm/llvm-project/blob/ec066d30e29fce388b1722971970d73ec65f14fb/lldb/test/API/lang/objc/exceptions/TestObjCExceptions.py#L239-L258
Thanks for taking a look. I haven't seen it very frequently, so will probably be tricky to reproduce. But I'll ping if it happens again
FYI, just saw this on the macOS Swift fork bots (running Intel): https://ci.swift.org/view/LLDB/job/oss-lldb-incremental-macos-cmake/8439/execution/node/423/log/
Do you know what version of clang is used on the swift build bots? It looks like the other test has a filter for @skipIf(compiler="clang", compiler_version=["<", "13.0"])
but I think thats a somewhat older version of clang, if I'm not mistaken.
I could add that filter to the lldb-dap test to be safe though.
I've seen this fail occasionally on the public macOS buildbots. Example: https://green.lab.llvm.org/job/llvm.org/view/LLDB/job/as-lldb-cmake/15188/execution/node/97/log/?consoleFull
This assertion was added in https://github.com/llvm/llvm-project/pull/105905