llvm-project

History

Adrian Prantl d913c86b93 don't use CHECK-NEXT because it may be on the same line. llvm-svn: 190969		2013-09-18 23:01:54 +00:00
..
README.txt	fix typos	2013-09-06 18:10:42 +00:00
aggregate-indirect-arg.cpp	Massage those regexps to work with both lldb and gdb.	2013-09-18 22:56:35 +00:00
block_var.m	XTARGET was removed, update debug-info tests.	2012-10-20 01:38:50 +00:00
blocks.m	XTARGET was removed, update debug-info tests.	2012-10-20 01:38:50 +00:00
ctor.cpp	Testcase for r133065	2011-06-15 17:57:23 +00:00
dbg-arg.c	Migrate dbg-arg.ll to a C file test to be resilient to IR changes.	2013-03-13 18:46:28 +00:00
foreach.m	XTARGET was removed, update debug-info tests.	2012-10-20 01:38:50 +00:00
forward-declare-class.cpp	Fix this for gdb 7.4.	2012-07-23 19:41:58 +00:00
llgdb.py	Auto-detect the architecture of the executable instead of using the arch of	2013-09-07 20:04:29 +00:00
nested-struct.cpp	Add an lldb wrapper script that implements gdb-compatible commands on top	2013-09-06 18:10:44 +00:00
sret.cpp	don't use CHECK-NEXT because it may be on the same line.	2013-09-18 23:01:54 +00:00
static-member.cpp	Use a more backwards-compatible method for evaluating expressions and add	2013-09-06 22:33:52 +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. Typically, test 
cases included here includes debugger commands and intended debugger output 
as comments in 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.