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.
22 lines
532 B
C++
22 lines
532 B
C++
// Purpose:
|
|
// Check the `view` subtool works with typical inputs.
|
|
//
|
|
// REQUIRES: system-linux, lldb
|
|
//
|
|
// RUN: %dexter_base test --fail-lt 1.0 -w \
|
|
// RUN: --builder 'clang' --debugger 'lldb' --cflags "-O0 -g" \
|
|
// RUN: --results %t -- %s
|
|
//
|
|
// RUN: %dexter_base view %t/view.cpp.dextIR | FileCheck %s
|
|
// CHECK: ## BEGIN
|
|
// CHECK: ## END
|
|
//
|
|
// # [TODO] This doesn't run if FileCheck fails!
|
|
// RUN: rm -rf %t
|
|
|
|
int main() {
|
|
int a = 0;
|
|
return 0; //DexLabel('ret')
|
|
}
|
|
// DexExpectWatchValue('a', '0', on_line='ret')
|