92ada4ab0c
Modifying the interpreter settings is tricky because they don't take effect until we create a new command interpreter, which should be merely an implementation detail. This leads to confusing and unexpected scenarios. This adds a test cases with FIXMEs for some of the odd scenarios I encountered. I didn't XFAIL the test because I don't think there's a way to get an unexpected PASS if any of the commands succeeds and splitting up the file in multiple tests seems excessive. llvm-svn: 371259
25 lines
1.1 KiB
Plaintext
25 lines
1.1 KiB
Plaintext
# Modifying the interpreter settings is tricky because they don't take effect
|
|
# until we create a new command interpreter, which should be merely an
|
|
# implementation detail. This leads to confusing and unexpected scenarios.
|
|
#
|
|
# Below are a few scenarios that we should fix.
|
|
|
|
# CONTINUE: 123456789
|
|
# STOP-NOT: 111111111
|
|
# STOP-NOT: 123456789
|
|
|
|
# FIXME: Should stop
|
|
# RUN: %lldb -b -o 'settings set interpreter.stop-command-source-on-error false' -s %S/Inputs/StopCommandSource.in | FileCheck %s --check-prefix CONTINUE
|
|
|
|
# FIXME: Should continue
|
|
# RUN: %lldb -b -s %S/Inputs/DontStopCommandSource.in -o 'bogus' -o 'print 111100000 + 11111' | FileCheck %s --check-prefix STOP
|
|
|
|
# FIXME: Should continue
|
|
# RUN: %lldb -b -o 'settings set interpreter.stop-command-source-on-error false' -o 'bogus' -o 'print 123400000 + 56789' | FileCheck %s --check-prefix STOP
|
|
|
|
# FIXME: Should continue
|
|
# RUN: %lldb -b -s %S/Inputs/DontStopCommandSource.in | FileCheck %s --check-prefix STOP
|
|
|
|
# FIXME: Should continue
|
|
# RUN: %lldb -b -o 'settings set interpreter.stop-command-source-on-error true' -s %S/Inputs/DontStopCommandSource.in | FileCheck %s --check-prefix STOP
|