bcm5719-llvm/debuginfo-tests, branch meklort-10.0.1

Add test for GDB pretty printers.

2020-01-11T08:17:15+00:00

Reviewers: dblaikie, aprantl, davide, JDevlieghere Reviewed By: aprantl Subscribers: jmorse, aprantl, merge_guards_bot, mgorny, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D72321

[debuginfo] Update test to account for missing __debug_macinfo

2019-11-11T18:40:47+00:00

We no longer emit this section if it's empty.

Don't attempt to upgrade debug-info-tests to Python3.

2019-11-08T22:14:12+00:00

There was CMake code that would attempt to detect Python 3 even if LLVM was configured with Python 2, but it messed with the environment for the other LLVM projects. This commit removes this functionality and just lkeaves a hard error if Python < 3 is detected and debuginfo-tests are required.

[dexter] Fix feature tests on Windows

2019-11-05T18:49:57+00:00

First, add LLD as a dependency on Windows. The windows batch scripts pass -fuse-ld=lld, so they need it. Second, decode builder stdout/stderr even if the command fails. Otherwise it gets printed as b'line 1\n\rline 2\n\r'. Last, make the batch script one line less noisy. We might want to try to do more here, though. It would be nice if we could get as close to possible as lit, where you can literally copy & paste the failing command to re-run it. With the two changes above, now the feature tests that use clang++.bat pass for me. The clang-cl_vs2015 ones still fail, and I'll fix them separately. Reviewers: jmorse Differential Revision: https://reviews.llvm.org/D69725

[dexter] Remove lit check for python 3

2019-11-05T18:49:56+00:00

This is checking the version of Python used to run lit, which is not necessarily the same as the version used to run the dexter tests. If the tests are run via the build/bin/llvm-lit[.py] helper script, then that is likely to pick up whatever version of Python is on PATH. Conventionally, this will find Python 2. CMake already checks that Python 3 is in use and puts the path to it in the lit site config, so this check is redundant, and Python 3 will ultimately be used to run dexter. Reviewers: jmorse Differential Revision: https://reviews.llvm.org/D69724

[debuginfo-tests] Don't look for Python 3 if we already have it

2019-11-01T18:24:39+00:00

LLDB already requires Python 3 on Windows, so I already configure it that way. For some reason CMake fails to find the one that Visual Studio automatically installs at this standard location: C:/Program Files (x86)/Microsoft Visual Studio/Shared/Python37_64/python.exe CMake prefers the python on path, which happens to be python 2.7. Reviewers: aprantl, jmorse Differential Revision: https://reviews.llvm.org/D69684

[Dexter] Continue sprinking no-location fixes

2019-11-01T13:57:52+00:00

Example failure: http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake/3255/testReport/junit/debuginfo-tests/dexter-tests/asan_c/ The tests themselves seem to be working, it's just unexplored paths within dexter that are flaking out.

[Dexter] Account for another no-lineno scenario

2019-11-01T13:41:56+00:00

This is another part of Dexter that had never seen a missing source location before, now newly turning up on Darwin.

[Dexter] Cope better with empty source locations

2019-11-01T13:30:26+00:00

When running a program, Dexter single steps if it's in one of the source files under test, or free-runs if it isn't. Handle the circumstance where the current source file simply isn't known.

Unmask dexter debuginfo tests on Darwin

2019-11-01T13:12:47+00:00

These tests almost certainly work on Darwin anyway, I just wanted to keep things in a fixed, working configuration, while pushing Dexter up. I've left Windows unsupported as the dexter command line will need further adjustment to run dbgeng. This can be abstracted through the %dexter substitution, but is a task for another time.