hanchenye-llvm-project/debuginfo-tests
Adrian Prantl 8ac899c600 Make nrvo-string test more robust.
The breakpoint locations were in places where clang doesn't actually
emit a source location for and depend on the debugger's ability to
move the breakpoint forward onto a line that is already in the
function epilogue. In my testing older versions of LLDB fail to do
that, so I'm modifying the test to force a break-able location by
calling a noinline function.

<rdar://problem/52079841>

llvm-svn: 364466
2019-06-26 20:04:09 +00:00
..
win_cdb Store a pointer to the return value in a static alloca and let the debugger use that 2019-06-20 17:15:21 +00:00
.arcconfig
CMakeLists.txt Move the pybool logic from CMake to Python for simplicity 2019-05-29 21:45:43 +00:00
README.txt
aggregate-indirect-arg.cpp
apple-accel.cpp
asan-blocks.c
asan-deque.cpp
asan.c
block_var.m
blocks.m
ctor.cpp
dbg-arg.c
foreach.m
forward-declare-class.cpp
lit.cfg.py [Python 3] Decode check_ouput result as UTF-8 2019-06-25 15:58:32 +00:00
lit.local.cfg
lit.site.cfg.py.in Move the pybool logic from CMake to Python for simplicity 2019-05-29 21:45:43 +00:00
llgdb.py llgdb.py: Make sure to clean up the debugger on exit. 2019-06-17 20:06:34 +00:00
nested-struct.cpp
nrvo-string.cpp Make nrvo-string test more robust. 2019-06-26 20:04:09 +00:00
safestack.c
sret.cpp
stack-var.c
static-member-2.cpp
static-member.cpp
test_debuginfo.pl
vla.c

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.