llvm-project

History

Stephen Tozer 73a01952b5 [Dexter] Add a simple logging class to Dexter Adds a basic logging class to Dexter that uses the existing PrettyOutput class for printing and supports 3 levels of verbosity (note, warning, error). Intended to consolidate the logging logic for Dexter into one place, removing the need for conditional log statements and making it easier for us later if we wish to use a more complete logging class. Reviewed By: Orlando Differential Revision: https://reviews.llvm.org/D144983		2023-03-15 19:25:37 +00:00
..
clang_llvm_roundtrip	[cross-project] Disable debug-types-section tests on Apple systems	2022-08-24 07:31:29 -04:00
dexter	[Dexter] Add a simple logging class to Dexter	2023-03-15 19:25:37 +00:00
dexter-tests	[dexter-tests] Add attribute optnone to main function	2022-10-26 20:57:49 +00:00
llgdb-tests	Walk back an overly-aggressive unXFAIL.	2023-02-03 17:22:32 -08:00
llvm-prettyprinters/gdb	[cross-project-tests] Use std::optional instead of llvm::Optional (NFC)	2023-01-14 20:56:10 -08:00
win_cdb-tests
lit.local.cfg
README.txt

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.