7b5dc63fc4
selecting the "Most relevant" frame. If you don't do that, then the correct frame gets selected, but it happens AFTER the frame info gets printed in the stop message, so you don't see the selected frame. The test for this hid the issue because it ran `frame info` and checked the result of that. That happens after the recognizer selects the frame, and so it was right. But if the recognizer is working correctly it will have already done the same printing in the stop message, and this way we also verify that the stop message was right. Differential Revision: https://reviews.llvm.org/D150315
19 lines
506 B
Plaintext
19 lines
506 B
Plaintext
# XFAIL: system-freebsd
|
|
# XFAIL: system-netbsd
|
|
#
|
|
# llvm.org/pr56144
|
|
# UNSUPPORTED: system-linux
|
|
#
|
|
# UNSUPPORTED: system-windows
|
|
# RUN: %clang_host -g -O0 %S/Inputs/assert.c -o %t.out
|
|
# RUN: %lldb -b -s %s %t.out | FileCheck %s
|
|
run
|
|
# CHECK: thread #{{.*}}stop reason = hit program assert
|
|
# CHECK: frame #{{.*}}`main at assert.c
|
|
frame recognizer info 0
|
|
# CHECK: frame 0 is recognized by Assert StackFrame Recognizer
|
|
set set thread-format "{${thread.stop-reason-raw}}\n"
|
|
thread info
|
|
# CHECK: signal SIGABRT
|
|
q
|