aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp
diff options
context:
space:
mode:
authorJohnny Chen <johnny.chen@apple.com>2011-06-22 21:15:10 +0000
committerJohnny Chen <johnny.chen@apple.com>2011-06-22 21:15:10 +0000
commitbfae99cf2900a03f5ba4c9aaa60006e4d307f29c (patch)
treead83073444845707a18c0a65d50ef9551f1bee62 /llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp
parent5dc6b794b15f5b21cd84601ad924fdb9530e97c9 (diff)
downloadllvm-bfae99cf2900a03f5ba4c9aaa60006e4d307f29c.zip
llvm-bfae99cf2900a03f5ba4c9aaa60006e4d307f29c.tar.gz
llvm-bfae99cf2900a03f5ba4c9aaa60006e4d307f29c.tar.bz2
Modify the test cases (there are a bunch of them) under test/types so that they
employ different executable names when creating the target for lldb to debug. Comparing the log files for the same test case with success/failure results show that the failed one was setting the breakpoint on some different address than the succeeded one, leading us to suspect that the file system maybe think it knows better and caches the wrong executable file (they were all named 'a.out' before) which lldb subsequently reads from. Now './dotest.py -v types' passes without specifying the '-w' option. rdar://problem/9644488 rdar://problem/9649573 llvm-svn: 133649
Diffstat (limited to 'llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp')
0 files changed, 0 insertions, 0 deletions