7f738c811a
I baked the "test" subcommand into the %dexter substituion, as that's what all of the dexter tests use. However I forgot about the internal tests for whether dexters features are working. Install a %dexter_base command to allow those tests to call dexter.py directly, and un-xfail the tests on darwin. Update too the list of paths the unittests shouldn't try and cover, as it tries to load dbgeng on unix machines. Ideally we wouldn't be using this method of test discovery in the future.
26 lines
778 B
C++
26 lines
778 B
C++
// Purpose:
|
|
// Check that parsing bad commands gives a useful error.
|
|
// - Syntax error (misplaced ',') over multiple lines
|
|
// Check directives are in check.txt to prevent dexter reading any embedded
|
|
// commands.
|
|
//
|
|
// Note: Despite using 'lldb' as the debugger, lldb is not actually required
|
|
// as the test should finish before lldb would be invoked.
|
|
//
|
|
// RUN: not %dexter_base test --builder 'clang' --debugger "lldb" \
|
|
// RUN: --cflags "-O0 -g" -v -- %s \
|
|
// RUN: | FileCheck %s --match-full-lines --strict-whitespace
|
|
//
|
|
// CHECK:parser error:{{.*}}err_syntax_mline.cpp(24): invalid syntax
|
|
// CHECK: ,'a', 3, 3, 3, 3, on_line=0)
|
|
// CHECK: ^
|
|
|
|
int main(){
|
|
return 0;
|
|
}
|
|
|
|
/*
|
|
DexExpectWatchValue(
|
|
,'a', 3, 3, 3, 3, on_line=0)
|
|
*/
|