llvm-project/cross-project-tests/debuginfo-tests
David Blaikie 1cee3d9db7 DebugInfo: Consider the type of NTTP when simplifying template names
Since the NTTP may need to be cast to the type when rebuilding the name,
check that the type can be rebuilt when determining whether a template
name can be simplified.
2022-04-08 00:00:46 +00:00
..
clang_llvm_roundtrip DebugInfo: Consider the type of NTTP when simplifying template names 2022-04-08 00:00:46 +00:00
dexter [Dexter] Optimize breakpoint deletion in Visual Studio 2022-03-01 13:13:38 +00:00
dexter-tests [cross-project-tests] Add REQUIRES: compiler-rt to tests that use asan 2022-02-10 10:48:03 +00:00
llgdb-tests [cross-project-tests] REQUIRES: system-darwin in llgdb-tests/asan-deque.cpp 2022-02-10 13:53:52 +00:00
llvm-prettyprinters/gdb [mlir] Finish removing Identifier from the C++ API 2022-01-12 11:58:23 -08:00
win_cdb-tests
README.txt
lit.local.cfg

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.