forked from OSchip/llvm-project
75d38f1e48
This is an initial prototype of how we can run debugger integration tests on Windows. cdb and windbg share a command language and debugger engine. Visual Studio has its own, but we should at least be able to use cdb as the basis for optimized debug info integration tests. There's a lot of work to do here still. For example: - Make fewer assumptions about the SDK location - Don't assume x64 (important, I need x86 testing) - More environment isolation, have lit setup vcvars instead of passing LIB and INCLUDE down. - Write a .py file to replace the grep+sed RUN line But, this seemed like a good enough concept to commit as is, since it's useful to me already. Reviewers: aprantl, zturner Differential Revision: https://reviews.llvm.org/D54187 llvm-svn: 361889 |
||
|---|---|---|
| .. | ||
| win_cdb | ||
| .arcconfig | ||
| CMakeLists.txt | ||
| 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 | ||
| lit.local.cfg | ||
| lit.site.cfg.py.in | ||
| llgdb.py | ||
| nested-struct.cpp | ||
| nrvo-string.cpp | ||
| 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.