aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Reader/MetadataLoader.cpp
diff options
context:
space:
mode:
authorJason Molenda <jason@molenda.com>2023-06-15 15:39:01 -0700
committerJason Molenda <jason@molenda.com>2023-06-15 15:41:37 -0700
commit6a8e2538afc10e6b7a321fd38bf5faf550518f2a (patch)
tree430af7a332cca489fec18d1c64da4e1f8bf8903c /llvm/lib/Bitcode/Reader/MetadataLoader.cpp
parent29aa587f1a0829a36c188301ea565e18c79a0b7b (diff)
downloadllvm-6a8e2538afc10e6b7a321fd38bf5faf550518f2a.zip
llvm-6a8e2538afc10e6b7a321fd38bf5faf550518f2a.tar.gz
llvm-6a8e2538afc10e6b7a321fd38bf5faf550518f2a.tar.bz2
Add a fatal error for debug builds when disagreement about stepping
On one CI bot we're seeing a failure where the kernel reports that we have completed an instruction step (via a mach exception) and lldb doesn't think the thread was doing an instruction step. It takes the conservative approach of stopping at this point, breaking tests. This patch adds an llvm fatal error for debug builds where it will log the state of the thread and the AArch64 ESR, to confirm what the hardware reported as the exception so we can double check the kernel's interpretation. I'll change this to an lldbassert without the runtime details in the string once we have an idea what is happening. the hope is that this will get hit on the CI bot soon. Differential Revision: https://reviews.llvm.org/D153079
Diffstat (limited to 'llvm/lib/Bitcode/Reader/MetadataLoader.cpp')
0 files changed, 0 insertions, 0 deletions