| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[LLDB] Run API tests with PDB too (#149305) From https://github.com/llvm/llvm-project/pull/148554#issuecomment-3083261858 - this adds an option for API tests to be run with the both PDB readers on Windows. As there are a lot of failures with PDB, this is an opt-in per test. To get PDB, -g -gcodeview has to be used on Clang. -gcodeview alone isn't enough, because it won't cause clang to pass -debug to the linker. #149498 tracks the (currently) failing tests. | 8 个月前 | |
[LLDB] Fix test compilation errors under asan (NFC) (#168408) https://green.lab.llvm.org/job/llvm.org/view/LLDB/job/lldb-cmake-sanitized/2744/consoleText | 8 个月前 | |
[lldb] fix(lldb/**.py): fix invalid escape sequences (#94034) Co-authored-by: Eisuke Kawashima <e-kwsm@users.noreply.github.com> | 1 年前 | |
[lldb-dap] Address a unit test race condition during initialization. (#167981) During the initialization sequence in our tests the first 'threads' response sould only be kept if the process is actually stopped, otherwise we will have stale data. In VSCode, during the debug session startup sequence immediately after 'configurationDone' a 'threads' request is made. This initial request is to retrieve the main threads name and id so the UI can be populated. However, in our tests we do not want to cache this value unless the process is actually stopped. We do need to make this initial request because lldb-dap is caching the initial thread list during configurationDone before the process is resumed. We need to make this call to ensure the cached initial threads are purged. I noticed this in a CI job for another review (https://github.com/llvm/llvm-project/actions/runs/19348261989/job/55353961798) where the tests incorrectly failed to fetch the threads prior to validating the thread names. | 8 个月前 | |
[lldb][docs] Remove/update docs pointing to unittest2 (#82672) | 2 年前 | |
[lldb] Remove use of __future__ in python These were useful primarily for the Python 2 to 3 transition. Python 2 is no longer supported so these are no longer necessary. Differential Revision: https://reviews.llvm.org/D157759 | 2 年前 | |
[lldb][test] Break early when walking backtrace in concurrent tests We only need to see that 1 frame of the stack is in user code. No need to carry on looking. Doing so actually caused a test failure on Armv8 Ubuntu Jammy where a libc function does not have a display name. I'm sure I'm going to get stung by this elsewhere, but for this test, breaking early sidesteps the problem. | 1 年前 | |
[lldb] Add utility to create Mach-O corefile from YAML desc (#153911) I've wanted a utility to create a corefile for test purposes given a bit of memory and regsters, for a while. I've written a few API tests over the years that needed exactly this capability -- we have several one-off Mach-O corefile creator utility in the API testsuite to do this. But it's a lot of boilerplate when you only want to specify some register contents and memory contents, to create an API test. This adds yaml2mach-core, a tool that should build on any system, takes a yaml description of register values for one or more threads, optionally memory values for one or more memory regions, and can take a list of UUIDs that will be added as LC_NOTE "load binary" metadata to the corefile so binaries can be loaded into virtual address space in a test scenario. The format of the yaml file looks like cpu: armv7m # optionally specify the number of bits used for addressing # (this line is from a different, 64-bit, yaml file) addressable-bits: num-bits: 39 # optionally specify one or more binary UUID and slide/virtual address to be added as an LC_NOTE # (this line is from a different, 64-bit, yaml file) binaries: - name: debug-binary.development uuid: 67942352-5857-3D3D-90CB-A3F80BA67B04 virtual-address: 0xfffffff01840c000 threads: - regsets: - flavor: gpr registers: [{name: sp, value: 0x2000fe70}, {name: r7, value: 0x2000fe80}, {name: pc, value: 0x0020392c}, {name: lr, value: 0x0020392d}] memory-regions: # stack memory - addr: 0x2000fe70 UInt32: [ 0x0000002a, 0x20010e58, 0x00203923, 0x00000001, 0x2000fe88, 0x00203911, 0x2000ffdc, 0xfffffff9 ] # instructions of a function - addr: 0x203910 UInt8: [ 0xf8, 0xb5, 0x04, 0xaf, 0x06, 0x4c, 0x07, 0x49, 0x74, 0xf0, 0x2e, 0xf8, 0x01, 0xac, 0x74, 0xf0 ] and that's all that is needed to specify a corefile where four register values are specified (the others will be set to 0), and two memory regions will be emitted. The memory can be specified as an array of UInt8, UInt32, or UInt64, I anticipate that some of these corefiles may have stack values constructed manually and it may be simpler for a human to write them in a particular grouping of values. I needed this utility for an upcoming patch for ARM Cortex-M processors, to create a test for the change. I took the opportunity to remove two of the "trivial mach-o corefile" creator utilities I've written in the past, which also restricted the tests to only run on Darwin systems because I was using the system headers for Mach-O constant values. rdar://110663219 | 10 个月前 | |
[debugserver] Support for qMemTags packet (#160952) Support for qMemTags packet in debugserver which allows usage of LLDB's memory tag read on Darwin. | 10 个月前 | |
[NFC][LLDB] Make it possible to detect if the compiler used in tests supports -fbounds-safety (#169112) This patch makes it possible to detect in LLDB shell and API tests if -fbounds-safety is supported by the compiler used for testing. The motivation behind this is to allow upstreaming https://github.com/swiftlang/llvm-project/pull/11835 but with the tests disabled in upstream because the full implementation of -fbounds-safety isn't available in Clang yet. For shell tests when -fbounds-safety is available the clang-bounds-safety feature is available which means tests can be annotated with # REQUIRES: clang-bounds-safety. API tests that need -fbounds-safety support in the compiler can use the new @skipUnlessBoundsSafety decorator. rdar://165225507 | 8 个月前 | |
[lldb][test] Don't run libc++ API tests without a locally built libc++ (#162657) API tests in the libc++ category will try their best to build against a locally built libc++. If none exists, the Makefile.rules currently fall back to using the system libc++. The issue with falling back to the system libc++ is that we are now potentially not testing what we intended to. But we also can't rely on certain libc++ features being available that the tests are trying to use. On Apple platforms this is a configuration error (because libc++ is the only stdlib supported), but we can't make it an error on Linux because a user might want to run the API tests with libstdc++. The Ubunutu 22.04 bots on the Apple fork are failing to run following tests are failing: * TestLibcxxInternalsRecognizer.py * TestDataFormatterStdRangesRefView.py because the system stdlib doesn't have std::ranges support yet. And the tests just fail to build. Building libc++ on those bots is also not possible because the system compiler is too old (and the Apple fork builds all the subprojects standalone, so it requires the system compiler). This patch marks tests in the libc++ category as UNSUPPORTED if no local libc++ is available. The downside is that we will inevitably lose coverage on bots that were running these tests without a local libc++. Arguably those weren't really testing the right thing. But for vendors with LLDB forks it might have been useful to at least know that the tests on the fork don't fail against the system libc++. Confirmed that the libc++ pre-merge CI still runs these tests (since it uses the explicit --category libc++ dotest flag). Also confirmed that LLDB pre-merge CI runs the tests (because it builds libcxx locally). **Workaround** If you do need want to run libc++ tests against the system stdlib, you can invoke lldb-dotest with the --category libc++ flag: ./path/to/build/lldb-dotest --category libc++ OR ./path/to/build/bin/llvm-lit -sv --param dotest-args='--category libc++' "/path/to/monorepo/lldb/test/API rdar://136231390 | 9 个月前 | |
| 1 年前 | ||
[lldb] Add bidirectional packetLog to gdbclientutils.py (#162176) While debugging the tests for #155000 I found it helpful to have both sides of the simulated gdb-rsp traffic rather than just the responses so I've extended the packetLog in MockGDBServerResponder to record traffic in both directions. Tests have been updated accordingly | 9 个月前 | |
[lldb][test] Remove LLDB_TEST_USE_VENDOR_PACKAGES (#89260) The LLDB_TEST_USE_VENDOR_PACKAGES has defaulted to Off for a while. Either installing pexpect or skipping those tests with -DLLDB_TEST_USER_ARGS=--skip-category=pexpect seems to be enough that we can fully remove this option. This patch removes the LLDB_TEST_USE_VENDOR_PACKAGES cmake configuration as well as the associated code to add third_party/Python/module to the python path. I'll do the actual deletion of third_party/Python/module in a followup PR in the (unlikely, I hope) event this commit needs to be reverted. | 2 年前 | |
[lldb] Remove use of __future__ in python These were useful primarily for the Python 2 to 3 transition. Python 2 is no longer supported so these are no longer necessary. Differential Revision: https://reviews.llvm.org/D157759 | 2 年前 | |
[NFC][Py Reformat] Reformat python files in lldb This is an ongoing series of commits that are reformatting our Python code. Reformatting is done with black (23.1.0). If you end up having problems merging this commit because you have made changes to a python file, the best way to handle that is to run git checkout --ours <yourfile> and then reformat it with black. RFC: https://discourse.llvm.org/t/rfc-document-and-standardize-python-code-style Differential revision: https://reviews.llvm.org/D151460 | 3 年前 | |
[lldb] Add bidirectional packetLog to gdbclientutils.py (#162176) While debugging the tests for #155000 I found it helpful to have both sides of the simulated gdb-rsp traffic rather than just the responses so I've extended the packetLog in MockGDBServerResponder to record traffic in both directions. Tests have been updated accordingly | 9 个月前 | |
Reapply "[lldb] Implement basic support for reverse-continue (#125242)" (again) (#128156) This reverts commit https://github.com/llvm/llvm-project/commit/87b7f63a117c340a6d9ca47959335fd7ef6c7ad2, reapplying https://github.com/llvm/llvm-project/commit/7e66cf74fb4e6a103f923e34700a7b6f20ac2a9b with a small (and probably temporary) change to generate more debug info to help with diagnosing buildbot issues. | 1 年前 | |
[lldb] Remove use of __future__ in python These were useful primarily for the Python 2 to 3 transition. Python 2 is no longer supported so these are no longer necessary. Differential Revision: https://reviews.llvm.org/D157759 | 2 年前 | |
[lldb] fix(lldb/**.py): fix invalid escape sequences (#94034) Co-authored-by: Eisuke Kawashima <e-kwsm@users.noreply.github.com> | 1 年前 | |
[lldb] Remove use of __future__ in python These were useful primarily for the Python 2 to 3 transition. Python 2 is no longer supported so these are no longer necessary. Differential Revision: https://reviews.llvm.org/D157759 | 2 年前 | |
Re-land "[lldb] Pick the builder for the target platform (#151262)" Pick the builder for the target platform, not the host platform. This is necessary when running the test suite remotely on a different platform. Unlike for Darwin, both Windows and Linux us the default builder, which is why this went unnoticed on the remote-linux bots. | 1 年前 | |
[lldb] Ignore registers that the debugserver fails to read (#132122) On Mac x86-64, the debugserver reports a register ('ds' at least) but returns an error when we try to read it. Just skip storing such registers in snapshots so we won't try to restore them. | 1 年前 | |
[LLDB] Run API tests with PDB too (#149305) From https://github.com/llvm/llvm-project/pull/148554#issuecomment-3083261858 - this adds an option for API tests to be run with the both PDB readers on Windows. As there are a lot of failures with PDB, this is an opt-in per test. To get PDB, -g -gcodeview has to be used on Clang. -gcodeview alone isn't enough, because it won't cause clang to pass -debug to the linker. #149498 tracks the (currently) failing tests. | 8 个月前 | |
[dotest] Add the ability to set environment variables for the inferior. This patch adds a dotest flag for setting environment variables for the inferior. This is different from the current --env flag, which sets variables in the debugger's environment. This allows us to set things like LD_LIBRARY_PATH for testing. Differential revision: https://reviews.llvm.org/D63790 llvm-svn: 364443 | 6 年前 | |
Decent to Descent (#154040) [lldb] Rename RecursiveDecentFormatter to RecursiveDescentFormatter (NFC) | 11 个月前 | |
[LLDB] Run API tests with PDB too (#149305) From https://github.com/llvm/llvm-project/pull/148554#issuecomment-3083261858 - this adds an option for API tests to be run with the both PDB readers on Windows. As there are a lot of failures with PDB, this is an opt-in per test. To get PDB, -g -gcodeview has to be used on Clang. -gcodeview alone isn't enough, because it won't cause clang to pass -debug to the linker. #149498 tracks the (currently) failing tests. | 8 个月前 | |
[lldb][test] Add pexpect category for tests that import pexpect (#84860) Instead of directly annotating pexpect-based tests with @skipIfWindows, we can tag them with a new pexpect category. We still automatically skip windows behavior by adding pexpect to the skip category list if the platform is windows, but also allow non-Windows users to skip them by configuring cmake with -DLLDB_TEST_USER_ARGS=--skip-category=pexpect As a prerequisite, remove the restriction that @add_test_categories can only apply to test cases, and we make the test runner look for categories on both the class and the test method. | 2 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 8 个月前 | ||
| 8 个月前 | ||
| 1 年前 | ||
| 8 个月前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 8 个月前 | ||
| 9 个月前 | ||
| 1 年前 | ||
| 9 个月前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 3 年前 | ||
| 9 个月前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 8 个月前 | ||
| 6 年前 | ||
| 11 个月前 | ||
| 8 个月前 | ||
| 2 年前 |