bcm5719-llvm/lldb/packages/Python/lldbsuite/test/functionalities, branch meklort-10.0.1

[lldb] Add expect_expr function for testing expression evaluation in dotests.

2020-01-15T12:04:04+00:00

Summary: This patch adds a new function to lldbtest: `expect_expr`. This function is supposed to replace the current approach of calling `expect`/`runCmd` with `expr`, `p` etc. `expect_expr` allows evaluating expressions and matching their value/summary/type/error message without having to do any string matching that might allow unintended passes (e.g., `self.expect("expr 3+4", substrs=["7"])` can unexpectedly pass for results like `(Class7) $0 = 7`, `(int) $7 = 22`, `(int) $0 = 77` and so on). This only uses the function in a few places to test and demonstrate it. I'll migrate the tests in follow up commits. Reviewers: JDevlieghere, shafik, labath Reviewed By: labath Subscribers: christof, abidh, lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D70314

[lldb/test] Add test for CMTime data formatter

2020-01-15T07:11:15+00:00

Add a test for the CMTime data formatter. The coverage report showed that this code path was untested.

[lldb][tests] Cleanup '.categories'

2020-01-10T13:39:38+00:00

Data formatters: Look through array element typedefs

2020-01-10T10:45:24+00:00

Summary: Motivation: When formatting an array of typedefed chars, we would like to display the array as a string. The string formatter currently does not trigger because the formatter lookup does not resolve typedefs for array elements (this behavior is inconsistent with pointers, for those we do look through pointee typedefs). This patch tries to make the array formatter lookup somewhat consistent with the pointer formatter lookup. Reviewers: teemperor, clayborg Reviewed By: teemperor, clayborg Subscribers: clayborg, lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D72133

When reading Aux file in chunks, read consecutive byte ranges

2020-01-10T00:05:38+00:00

qemu has a very small maximum packet size (4096) and it actually only uses half of that buffer for some implementation reason, so when lldb asks for the register target definitions, the x86_64 definition is larger than 4096/2 and we need to fetch it in two parts. This patch and test is fixing a bug in GDBRemoteCommunicationClient::ReadExtFeature when reading a target file in multiple parts. lldb was assuming that it would always get back the maximum packet size response (4096) instead of using the actual size received and asking for the next group of bytes. We now have two tests in gdb_remote_client for unique features of qemu - TestNestedRegDefinitions.py would test the ability of lldb to follow multiple levels of xml includes; I opted to create a separate TestRegDefinitionInParts.py test to test this wrinkle in qemu's gdb remote serial protocol stub implementation. Instead of combining both tests into a single test file.

tests: XFAIL/UNSUPPORTED tests on Windows

2020-01-01T22:22:49+00:00

Now that we are building the python bindings on Windows once more, the extended testsuite is running. Mark a few failing tests and skip a few tests which hang. This should at least bring the bot back to green without reverting the Python changes which are an improvement for the build system and enable another ~35% of the test suite which was previously disabled.

[lldb][tests] Posix function strdup requires macro _POSIX_C_SOURCE

2019-12-26T15:49:34+00:00

test: ensure that we dead-strip in the linker

2019-12-24T18:19:22+00:00

`/OPT:REF` is needed for link to dead strip functions, `/Gy` by itself is not sufficient.

test: correct flags for Windows

2019-12-24T04:21:26+00:00

Adjust the flags for the LLDB test on Windows. This test was previously not running, but after the fix to the python detection, we now run this.

[lldb] Remove XFAIL from TestDeadStrip.py

2019-12-20T09:04:25+00:00

Fixed by 92211b.