summaryrefslogtreecommitdiffstats
path: root/debuginfo-tests
Commit message (Collapse)AuthorAgeFilesLines
* Make nrvo-string test more robust.Adrian Prantl2019-06-271-3/+4
| | | | | | | | | | | | | | | | This is a follow-up to r364466, but better implemented. Original commit message still applies: 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: 364589
* Make nrvo-string test more robust.Adrian Prantl2019-06-261-2/+5
| | | | | | | | | | | | | 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
* [Python 3] Decode check_ouput result as UTF-8Jonas Devlieghere2019-06-251-1/+1
| | | | llvm-svn: 364325
* Store a pointer to the return value in a static alloca and let the debugger ↵Amy Huang2019-06-202-2/+72
| | | | | | | | | | | | | | use that as the variable address for NRVO variables. Subscribers: hiraditya, cfe-commits, llvm-commits Tags: #clang, #llvm Differential Revision: https://reviews.llvm.org/D63361 llvm-svn: 363952
* llgdb.py: Make sure to clean up the debugger on exit.Adrian Prantl2019-06-171-1/+6
| | | | | | <rdar://problem/51807962> llvm-svn: 363611
* Add cdb test for global constantsAmy Huang2019-06-061-0/+33
| | | | | | | | | | | | | | Summary: This creates an integration test for global constants Reviewers: rnk Subscribers: llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D62974 llvm-svn: 362745
* Add cdb test for inline line tablesReid Kleckner2019-06-031-0/+45
| | | | | | | | | | | | | | | This creates an integration test for inlined call line tables, and in particular, ones that are discontiguous. We've had issues in the past with discontiguous inline line tables, and until r362429 LLD didn't write the inlinees section into the PDB. The test was reduced from https://crbug.com/965670 Reviewers: thakis Differential Revision: https://reviews.llvm.org/D62758 llvm-svn: 362431
* Move the pybool logic from CMake to Python for simplicityReid Kleckner2019-05-292-4/+1
| | | | | | | This is how similar booleans are handled, and seems to work for me locally. llvm-svn: 362039
* Add debuginfo-tests that use cdb on WindowsReid Kleckner2019-05-287-5/+90
| | | | | | | | | | | | | | | | | | | | | | | 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
* Set config.lit_tools_dir, which is needed by lit.llvm.initialize.Reid Kleckner2018-11-061-0/+1
| | | | llvm-svn: 346271
* [debuginfo-tests] commands.getoutput -> subprocess.check_outputFangrui Song2018-11-031-2/+2
| | | | | | | We should also make Darwin Python3 happy after r346059 The output has an extra newline but it is fine in this particular case. llvm-svn: 346066
* Update debuginfo tests lit for r341135Reid Kleckner2018-11-031-1/+2
| | | | llvm-svn: 346060
* [debuginfo-tests] Avoid "import commands" which was deprecated in Py3Reid Kleckner2018-11-031-1/+1
| | | | llvm-svn: 346059
* Revert "(Retry) Add a basic integration test for C++ smart pointers"Vedant Kumar2018-08-201-41/+0
| | | | | | | This reverts r340189. The new test is still failing on some Apple-internal bots. llvm-svn: 340204
* (Retry) Add a basic integration test for C++ smart pointersVedant Kumar2018-08-201-0/+41
| | | | | | | | | | | | Check that the debugger can pretty-print unique_ptr and shared_ptr when passed as a function argument. This was reverted in r339961 because of a bug in the version of lldb installed on the public Green Dragon builders. rdar://42314305 llvm-svn: 340189
* Revert "Add a basic integration test for C++ smart pointers"Bruno Cardoso Lopes2018-08-181-41/+0
| | | | | | | | | | | This reverts commit 73786631984289b3d601034b2bf4ba2b8f5845eb. Revert r339961 since its causing debuginfo-tests to fail: http://green.lab.llvm.org/green/job/clang-stage1-configure-RA/48514/ rdar://problem/43449629 llvm-svn: 340119
* Add a basic integration test for C++ smart pointersVedant Kumar2018-08-161-0/+41
| | | | | | | | | Check that the debugger can pretty-print unique_ptr and shared_ptr when passed as a function argument. rdar://42314305 llvm-svn: 339961
* SafeStack: Disable Darwin supportVlad Tsyrklevich2018-08-141-0/+1
| | | | | | | SafeStack support for Darwin has not been functional and was disabled in r339719/r339720. Disable Darwin for the safestack debuginfo test. llvm-svn: 339732
* Disable the asan-deque.cpp integration test for AppleLLDB < v1000Vedant Kumar2018-08-042-1/+10
| | | | | | | | | | | | | | | | | | | | | | Some of Apple's public CI nodes ship an lldb which has trouble debugging the asan-deque.cpp test. Specifically, that lldb appears to either parse location lists in the test program incorrectly or to have a broken std::deque data formatter. We don't want to work around this by weakening the integration test, and we're unable to update the lldb version on the CI node at the moment. The compromise is to require AppleLLDB >= 1000 when AppleLLDB is being used to debug this test. Reviewed (in person) by Adrian Prantl. Bot failure: http://lab.llvm.org:8080/green/job/clang-stage1-configure-RA/48074 rdar://42892721 llvm-svn: 338937
* [DWARF] Change a test to ensure the creation of a __debug_ranges section.Wolfgang Pieb2018-07-311-0/+3
| | | | | Reviewer: aprantl llvm-svn: 338424
* [debuginfo-tests] tweak new test to be compatible with wider range of compilers.Tim Northover2018-07-311-2/+2
| | | | | | | | emplace_back was added in C++11, and its usage isn't critical to what's being tested so using push_back instead will allow this test to work with more compilers. llvm-svn: 338371
* [DebugInfo] LowerDbgDeclare: Add derefs when handling CallInst usersVedant Kumar2018-07-261-0/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | LowerDbgDeclare inserts a dbg.value before each use of an address described by a dbg.declare. When inserting a dbg.value before a CallInst use, however, it fails to append DW_OP_deref to the DIExpression. The DW_OP_deref is needed to reflect the fact that a dbg.value describes a source variable directly (as opposed to a dbg.declare, which relies on pointer indirection). This patch adds in the DW_OP_deref where needed. This results in the correct values being shown during a debug session for a program compiled with ASan and optimizations (see https://reviews.llvm.org/D49520). Note that ConvertDebugDeclareToDebugValue is already correct -- no changes there were needed. One complication is that SelectionDAG is unable to distinguish between direct and indirect frame-index (FRAMEIX) SDDbgValues. This patch also fixes this long-standing issue in order to not regress integration tests relying on the incorrect assumption that all frame-index SDDbgValues are indirect. This is a necessary fix: the newly-added DW_OP_derefs cannot be lowered properly otherwise. Basically the fix prevents a direct SDDbgValue with DIExpression(DW_OP_deref) from being dereferenced twice by a debugger. There were a handful of tests relying on this incorrect "FRAMEIX => indirect" assumption which actually had incorrect DW_AT_locations: these are all fixed up in this patch. Testing: - check-llvm, and an end-to-end test using lldb to debug an optimized program. - Existing unit tests for DIExpression::appendToStack fully cover the new DIExpression::append utility. - check-debuginfo (the debug info integration tests) Differential Revision: https://reviews.llvm.org/D49454 llvm-svn: 338069
* Revert "[CMake] Sort dependency list and add safestack to it"Vedant Kumar2018-07-181-2/+1
| | | | | | | | | This reverts commit r337412. An Apple-internal bot cannot find the safestack dependency, and fails to configure with this change. llvm-svn: 337421
* [CMake] Sort dependency list and add safestack to itVedant Kumar2018-07-181-1/+2
| | | | | | The 'safestack.c' test requires safestack as a dependency. llvm-svn: 337412
* [debuginfo-tests] Always use the system python to invoke llgdb.py.Ahmed Bougacha2018-06-101-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | /usr/bin/env is recommended as a cross-platform way to find python. But: - we're only using lldb on darwin, where we know python (or at least, the xcrun-style shortcut) is in /usr/bin/ - the python interpreter in LLDB comes from /S/L/F: $ otool -L Contents/SharedFrameworks/LLDB.framework/LLDB | grep Python /System/Library/Frameworks/Python.framework/Versions/2.7/Python so when we use the lldb python module, it calls into the swig/python support in the lldb framework, and if there's a mismatch between the interpreter and the linked python, weird things occur. In theory, I believe this should be done by: - looking for the LLDB framework (llgdb.py does some of that) - finding the binary inside the framework - looking for the Python it was linked against (otool -L) - finding the interpreter executable inside the Python.framework But in practice, that's only different if we use a custom LLDB framework/pythonpath when running these tests, and AFAIK nobody does that right now, so the code would be dead anyway. Don't pretend we can use any arbitrary python: just use the system one. Differential Revision: https://reviews.llvm.org/D47967 llvm-svn: 334369
* [Darwin] Specify DWARF 2/4 when running apple accelerator tests.Davide Italiano2018-02-262-1/+6
| | | | | | | | | | These sections will be retired. Also, explicitly list llvm-objdump as a dependency. This should've been done in the previous commit, but I failed to squash the two changes together. Thanks to Adrian for pointing the first problem out in a comment. llvm-svn: 326121
* [Darwin] Add a test to make sure clang emits __apple accelerator tables.Davide Italiano2018-02-231-0/+17
| | | | llvm-svn: 325928
* [debuginfo-tests] Support moving debuginfo-tests to llvm/projectsDon Hinton2017-12-125-0/+197
| | | | | | | | | | | | | | | | | | | | Summary: Add cmake and lit files needed to run these tests as an external project. Also, copy test_debuginfo.pl from llvm/utils since it's only used here. The copy in llvm/utils must be maintained as long as bots continue to include debuginfo-tests in clang/test. This patch depends on clang patch https://reviews.llvm.org/D41055. Reviewers: zturner, aprantl Reviewed By: aprantl Subscribers: mgorny, llvm-commits, JDevlieghere Differential Revision: https://reviews.llvm.org/D40971 llvm-svn: 320495
* Revert "Temporarily pin tests to DWARF v2 until a more recent version of LLDB"Adrian Prantl2017-12-075-6/+6
| | | | | | | | This reverts commit 319790. We worked around the bug in LLVM instead. llvm-svn: 320076
* Temporarily pin tests to DWARF v2 until a more recent version of LLDBAdrian Prantl2017-12-055-6/+6
| | | | | | is available on green dragon. llvm-svn: 319790
* Re-revert "Refactor debuginfo-tests."Zachary Turner2017-11-2122-146/+16
| | | | | | | | | | This is still breaking greendragon. At this point I give up until someone can fix the greendragon bots, and I will probably abandon this effort in favor of using a private github repository. llvm-svn: 318722
* Resubmit "Refactor debuginfo-tests" again.Zachary Turner2017-11-2022-16/+146
| | | | | | | | | | | | This was reverted due to the tests being run twice on some build bots. Each run had a slightly different configuration due to the way in which it was being invoked. This fixes the problem (albeit in a somewhat hacky way). Hopefully in the future we can get rid of the workflow of running debuginfo-tests as part of clang, and then this hack can go away. llvm-svn: 318697
* Re-revert "Refactor debuginfo-tests"Zachary Turner2017-11-1722-136/+16
| | | | | | | | | | | | | | | | | | | | | | This is still broken because it causes certain tests to be run twice with slightly different configurations, which is wrong in some cases. You can observe this by running: ninja -nv check-all | grep debuginfo-tests And seeing that it passes clang/test and clang/test/debuginfo-tests to lit, which causes it to run debuginfo-tests twice. The fix is going to involve either: a) figuring out that we're running in this "deprecated" configuration, and then deleting the clang/test/debuginfo-tests path, which should cause it to behave identically to before, or: b) make lit smart enough that it doesn't descend into a sub-suite if that sub-suite already has a lit.cfg file. llvm-svn: 318486
* Resubmit "Refactor debuginfo-tests"Zachary Turner2017-11-1622-16/+136
| | | | | | | | | | This was reverted due to some failures on specific darwin buildbots, the issue being that the new lit configuration was not setting the SDKROOT environment variable. We've tested a fix locally and confirmed that it works, so this patch resubmits everything with the fix applied. llvm-svn: 318435
* Revert "Update test_debuginfo.pl script to point to new tree location."Zachary Turner2017-11-1322-134/+16
| | | | | | | | This reverts the aforementioned patch and 2 subsequent follow-ups, as some buildbots are still failing 2 tests because of it. Investigation is ongoing into the cause of the failures. llvm-svn: 318112
* [debuginfo-tests] Make debuginfo-tests work in a standard configuration.Zachary Turner2017-11-1022-16/+134
| | | | | | | | | | | | | | | | | | | Previously, debuginfo-tests was expected to be checked out into clang/test and then the tests would automatically run as part of check-clang. This is not a standard workflow for handling external projects, and it brings with it some serious drawbacks such as the inability to depend on things other than clang, which we will need going forward. The goal of this patch is to migrate towards a more standard workflow. To ease the transition for build bot maintainers, this patch tries not to break the existing workflow, but instead simply deprecate it to give maintainers a chance to update the build infrastructure. Differential Revision: https://reviews.llvm.org/D39605 llvm-svn: 317925
* Revert r313600 due to bot failures on Green Dragon.Mike Edwards2017-09-191-0/+2
| | | | | | http://green.lab.llvm.org/green/job/clang-stage1-configure-RA_check/35585/ llvm-svn: 313634
* Drop -O1 case from nrvo-string.cppHans Wennborg2017-09-181-2/+0
| | | | | | It relied on r313400 which was reverted in r313589. llvm-svn: 313600
* [debuginfo-tests] Add string NRVO test for PR34513Reid Kleckner2017-09-151-0/+27
| | | | | | It should pass in -O0 and -O1 after r313400 and r313399. llvm-svn: 313401
* Restrict debuginfo-tests to native configurations.Paul Robinson2017-09-081-0/+3
| | | | llvm-svn: 312803
* Fix debuginfo-tests with GDB on LinuxReid Kleckner2017-08-315-32/+80
| | | | | | | | | | | | | | | | | | | | | | | | | | | Summary: Split asan.c into asan.c and asan-blocks.c, which will be darwin-specific. I suspect we could make it pass on Linux by adding cmake to build BlocksRuntime from compiler-rt, but I'm not shaving that yak yet. asan.c and safestack.c: GDB and LLDB appear to print aggregates differently today. Print individual elements instead of the entire aggregate. dbg-arg.c: GDB doesn't appear to print leading zeros when printing pointers. stack-var.c: Add the optnone attribute so that LLVM won't optimize away this no-op function call. This should be a cross-platform failure observable on Mac, so this is surprising. Reviewers: aprantl, dblaikie Subscribers: llvm-commits Differential Revision: https://reviews.llvm.org/D37344 llvm-svn: 312265
* Add a test for PR33166.Adrian Prantl2017-05-251-0/+18
| | | | | | | This tests optimized code where a variable is allocated on the stack for some part of the function. llvm-svn: 303903
* Add additional CHECKs to safestack.c.Adrian Prantl2017-04-171-10/+20
| | | | llvm-svn: 300469
* Revert "Revert "Add a test for debug info with the safestack sanitizer ↵Adrian Prantl2017-04-171-0/+25
| | | | | | | | enabled."" This reapplies commit r299730 with an additional REQUIRES line. llvm-svn: 300468
* Revert "Revert "Add a test for __block variables + asan.""Adrian Prantl2017-04-172-9/+27
| | | | | | This reapplies commit r300228. llvm-svn: 300467
* Revert "Revert "Add an end-to-end testcase for address sanitizer.""Adrian Prantl2017-04-171-0/+26
| | | | | | This reapplies r299731 and adds an appropriate REQUIRES line. llvm-svn: 300466
* Revert "Add a test for debug info with the safestack sanitizer enabled."Ahmed Bougacha2017-04-171-21/+0
| | | | | | | | | This reverts commit r299730. It's causing failures on a bot because of missing compiler-rt: http://green.lab.llvm.org/green/job/clang-stage2-cmake-RgSan_check llvm-svn: 300460
* Revert "Add an end-to-end testcase for address sanitizer."Ahmed Bougacha2017-04-171-23/+0
| | | | | | | | | This reverts commit r299731. It's causing failures on a bot because of missing compiler-rt: http://green.lab.llvm.org/green/job/clang-stage2-cmake-RgSan_check llvm-svn: 300459
* Revert "Add a test for __block variables + asan."Ahmed Bougacha2017-04-172-28/+7
| | | | | | | | | This reverts commit r300228. It's causing failures on a bot because of missing compiler-rt: http://green.lab.llvm.org/green/job/clang-stage2-cmake-RgSan_check llvm-svn: 300458
* Add a test for __block variables + asan.Adrian Prantl2017-04-132-7/+28
| | | | llvm-svn: 300228
OpenPOWER on IntegriCloud