llvm-project/debuginfo-tests
Tom Weaver fc0acd10c0 [Dexter] Remove erroneously added diff file
Delete d.diff from debuginfo-tests/dexter directory.
2021-05-25 13:36:11 +01:00
..
dexter [Dexter] Remove erroneously added diff file 2021-05-25 13:36:11 +01:00
dexter-tests [dexter] Change line label reference syntax to enable label-relative offsets (2/2) 2021-05-21 08:58:58 +01:00
llgdb-tests Prefer /usr/bin/env xxx over /usr/bin/xxx where xxx = perl, python, awk 2021-02-25 11:32:27 +01:00
llvm-prettyprinters/gdb debuginfo-tests: Fix check-gdb-mlir-support build after MLIR API change in a4bb667d83 2021-03-15 05:10:15 +00:00
win_cdb-tests
CMakeLists.txt [debuginfo-tests] Remove explicit checks for Python 3 2021-02-15 14:20:55 +00:00
README.txt
lit.cfg.py [debuginfo-tests] Stop using installed LLDB and remove redundancy 2021-05-24 10:16:36 +01:00
lit.site.cfg.py.in [dexter] Force dexter tests to use the host triple 2021-02-24 11:11:17 +00:00

README.txt

                                                                   -*- rst -*-
This is a collection of tests to check debugging information generated by 
compiler. This test suite can be checked out inside clang/test folder. This 
will enable 'make test' for clang to pick up these tests.

Some tests (in the 'llgdb-tests' directory) are written with debugger
commands and checks for the intended debugger output in the source file,
using DEBUGGER: and CHECK: as prefixes respectively.

For example::

  define i32 @f1(i32 %i) nounwind ssp {
  ; DEBUGGER: break f1
  ; DEBUGGER: r
  ; DEBUGGER: p i 
  ; CHECK: $1 = 42 
  entry:
  }

is a testcase where the debugger is asked to break at function 'f1' and 
print value of argument 'i'. The expected value of 'i' is 42 in this case.

Other tests are written for use with the 'Dexter' tool (in the 'dexter-tests'
and 'dexter' directories respectively). These use a domain specific language
in comments to describe the intended debugger experience in a more abstract
way than debugger commands. This allows for testing integration across
multiple debuggers from one input language.

For example::

  void __attribute__((noinline, optnone)) bar(int *test) {}
  int main() {
    int test;
    test = 23;
    bar(&test); // DexLabel('before_bar')
    return test; // DexLabel('after_bar')
  }

  // DexExpectWatchValue('test', '23', on_line='before_bar')
  // DexExpectWatchValue('test', '23', on_line='after_bar')

Labels two lines with the names 'before_bar' and 'after_bar', and records that
the 'test' variable is expected to have the value 23 on both of them.