llvm-project/debuginfo-tests
Christian Sigg 97431831e5 Add pretty printers for llvm::PointerIntPair and llvm::PointerUnion.
Reviewers: aprantl, dblaikie, jdoerfert, nicolasvasilache

Reviewed By: dblaikie

Subscribers: jpienaar, dexonsmith, merge_guards_bot, llvm-commits

Tags: #llvm, #clang, #lldb, #openmp

Differential Revision: https://reviews.llvm.org/D72557
2020-01-27 17:23:59 +01:00
..
dexter [dexter] Fix feature tests on Windows 2019-11-05 10:49:57 -08:00
dexter-tests Unmask dexter debuginfo tests on Darwin 2019-11-01 13:12:47 +00:00
llgdb-tests [debuginfo] Update test to account for missing __debug_macinfo 2019-11-11 10:40:47 -08:00
llvm-prettyprinters/gdb Add pretty printers for llvm::PointerIntPair and llvm::PointerUnion. 2020-01-27 17:23:59 +01:00
win_cdb-tests Reapply "Import Dexter to debuginfo-tests"" 2019-10-31 16:51:53 +00:00
.arcconfig [debuginfo-tests] Support moving debuginfo-tests to llvm/projects 2017-12-12 16:54:20 +00:00
CMakeLists.txt Add test for GDB pretty printers. 2020-01-11 09:17:15 +01:00
README.txt Reapply "Import Dexter to debuginfo-tests"" 2019-10-31 16:51:53 +00:00
lit.cfg.py Add test for GDB pretty printers. 2020-01-11 09:17:15 +01:00
lit.site.cfg.py.in Reapply "Import Dexter to debuginfo-tests"" 2019-10-31 16:51:53 +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.