| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[lldb] Use assertState in even more tests (NFC) Followup to D127355 and D127378, converting more instances of assertEqual to assertState. | 3 年前 | |
[lldb][tests] Automatically call compute_mydir (NFC) Eliminate boilerplate of having each test manually assign to mydir by calling compute_mydir in lldbtest.py. Differential Revision: https://reviews.llvm.org/D128077 | 3 年前 | |
[lldb][ARM] Add tests for vpush/vpop D registers Previously we just checked via S regs and were not checking memory content after pushes. The vpush test confirms that the fix in https://reviews.llvm.org/D130307 is working. Memory will only be checked if an "after" state is provided. Reviewed By: clayborg Differential Revision: https://reviews.llvm.org/D130468 | 3 年前 | |
[lldb][tests] Automatically call compute_mydir (NFC) Eliminate boilerplate of having each test manually assign to mydir by calling compute_mydir in lldbtest.py. Differential Revision: https://reviews.llvm.org/D128077 | 3 年前 | |
[lldb][tests] Automatically call compute_mydir (NFC) Eliminate boilerplate of having each test manually assign to mydir by calling compute_mydir in lldbtest.py. Differential Revision: https://reviews.llvm.org/D128077 | 3 年前 | |
[lldb] Disable TestStackFromStdModule.py TestStackFromStdModule.py started failing due to f4fb72e6d4ce (https://reviews.llvm.org/D128146), with a clang assertion failure: assert(isa<InjectedClassNameType>(Decl->TypeForDecl)) | 3 年前 | |
[lldb][tests] Automatically call compute_mydir (NFC) Eliminate boilerplate of having each test manually assign to mydir by calling compute_mydir in lldbtest.py. Differential Revision: https://reviews.llvm.org/D128077 | 3 年前 | |
[lldb] Adapt lldb tests to changes in 71cdb8c6f144 | 3 年前 | |
[lldb][tests] Automatically call compute_mydir (NFC) Eliminate boilerplate of having each test manually assign to mydir by calling compute_mydir in lldbtest.py. Differential Revision: https://reviews.llvm.org/D128077 | 3 年前 | |
[lldb] Automatically unwrap parameter packs in template argument accessors When looking at template arguments in LLDB, we usually care about what the user passed in his code, not whether some of those arguments where passed as a variadic parameter pack. This patch extends all the C++ APIs to look at template parameters to take an additional 'expand_pack' boolean that automatically unwraps the potential argument packs. The equivalent SBAPI calls have been changed to pass true for this parameter. A byproduct of the patch is to also fix the support for template type that have only a parameter pack as argument (like the OnlyPack type in the test). Those were not recognized as template instanciations before. The added test verifies that the SBAPI is able to iterate over the arguments of a variadic template. The original patch was written by Fred Riss almost 4 years ago. Differential revision: https://reviews.llvm.org/D51387 (cherry picked from commit b706f56133a77f9d7c55270ac24ff59e6fce3fa4) | 3 年前 | |
[lldb][AArch64] Add support for memory tags in core files This teaches ProcessElfCore to recognise the MTE tag segments. https://www.kernel.org/doc/html/latest/arm64/memory-tagging-extension.html#core-dump-support These segments contain all the tags for a matching memory segment which will have the same size in virtual address terms. In real terms it's 2 tags per byte so the data in the segment is much smaller. Since MTE is the only tag type supported I have hardcoded some things to those values. We could and should support more formats as they appear but doing so now would leave code untested until that happens. A few things to note: * /proc/pid/smaps is not in the core file, only the details you have in "maps". Meaning we mark a region tagged only if it has a tag segment. * A core file supports memory tagging if it has at least 1 memory tag segment, there is no other flag we can check to tell if memory tagging was enabled. (unlike a live process that can support memory tagging even if there are currently no tagged memory regions) Tests have been added at the commands level for a core file with mte and without. There is a lot of overlap between the "memory tag read" tests here and the unit tests for MemoryTagManagerAArch64MTE::UnpackTagsFromCoreFileSegment, but I think it's worth keeping to check ProcessElfCore doesn't cause an assert. Depends on D129487 Reviewed By: omjavaid Differential Revision: https://reviews.llvm.org/D129489 | 3 年前 | |
[lldb] Improve the error message in run_to_breakpoint_do_run Improve the error message when we fail to hit the initial breakpoint in run_to_breakpoint_do_run. In addition to the process state, we now also report the exit code and reason (if the process exited) as well as the inferior's output. Differential revision: https://reviews.llvm.org/D111978 | 3 年前 | |
[lldb][tests] Automatically call compute_mydir (NFC) Eliminate boilerplate of having each test manually assign to mydir by calling compute_mydir in lldbtest.py. Differential Revision: https://reviews.llvm.org/D128077 | 3 年前 | |
[lldb] Adapt lldb tests to changes in 71cdb8c6f144 | 3 年前 | |
[LLDB] Fix TestThreadAPI.py for AArch64/Windows This patch fixes TestThreadAPI for AArch64 windows by switching over to PDB debug info instead of DWARF. This is needed to step over library functions like printf as there is debug info mismatch between DWARF and PDB. PDB DWARF interworking is not fully supported by LLDB at the moment. | 3 年前 | |
[lldb] Use assertState in even more tests (NFC) Followup to D127355 and D127378, converting more instances of assertEqual to assertState. | 3 年前 | |
[lldb][tests] Automatically call compute_mydir (NFC) Eliminate boilerplate of having each test manually assign to mydir by calling compute_mydir in lldbtest.py. Differential Revision: https://reviews.llvm.org/D128077 | 3 年前 | |
[lldb][tests] Automatically call compute_mydir (NFC) Eliminate boilerplate of having each test manually assign to mydir by calling compute_mydir in lldbtest.py. Differential Revision: https://reviews.llvm.org/D128077 | 3 年前 | |
[lldb][tests] Automatically call compute_mydir (NFC) Eliminate boilerplate of having each test manually assign to mydir by calling compute_mydir in lldbtest.py. Differential Revision: https://reviews.llvm.org/D128077 | 3 年前 | |
[lldb][tests] Automatically call compute_mydir (NFC) Eliminate boilerplate of having each test manually assign to mydir by calling compute_mydir in lldbtest.py. Differential Revision: https://reviews.llvm.org/D128077 | 3 年前 | |
[lldb][tests] Automatically call compute_mydir (NFC) Eliminate boilerplate of having each test manually assign to mydir by calling compute_mydir in lldbtest.py. Differential Revision: https://reviews.llvm.org/D128077 | 3 年前 | |
[lldb][tests] Automatically call compute_mydir (NFC) Eliminate boilerplate of having each test manually assign to mydir by calling compute_mydir in lldbtest.py. Differential Revision: https://reviews.llvm.org/D128077 | 3 年前 | |
[lldb][test] Remove symlink for API tests. Summary: Moves lldbsuite tests to lldb/test/API. This is a largely mechanical change, moved with the following steps: rm lldb/test/API/testcases mkdir -p lldb/test/API/{test_runner/test,tools/lldb-{server,vscode}} mv lldb/packages/Python/lldbsuite/test/test_runner/test lldb/test/API/test_runner for d in $(find lldb/packages/Python/lldbsuite/test/* -maxdepth 0 -type d | egrep -v "make|plugins|test_runner|tools"); do mv $d lldb/test/API; done for d in $(find lldb/packages/Python/lldbsuite/test/tools/lldb-vscode -maxdepth 1 -mindepth 1 | grep -v ".py"); do mv $d lldb/test/API/tools/lldb-vscode; done for d in $(find lldb/packages/Python/lldbsuite/test/tools/lldb-server -maxdepth 1 -mindepth 1 | egrep -v "gdbremote_testcase.py|lldbgdbserverutils.py|socket_packet_pump.py"); do mv $d lldb/test/API/tools/lldb-server; done lldb/packages/Python/lldbsuite/__init__.py and lldb/test/API/lit.cfg.py were also updated with the new directory structure. Reviewers: labath, JDevlieghere Tags: #lldb Differential Revision: https://reviews.llvm.org/D71151 | 6 年前 | |
[lldb][tests] Automatically call compute_mydir (NFC) Eliminate boilerplate of having each test manually assign to mydir by calling compute_mydir in lldbtest.py. Differential Revision: https://reviews.llvm.org/D128077 | 3 年前 | |
[lldb/test] Fix flakyness in TestNonStop.test_stdio The test was assuming that the output will come in two messages. The truth is that it will come in **at least** two messages. | 3 年前 | |
[lldb][tests] Automatically call compute_mydir (NFC) Eliminate boilerplate of having each test manually assign to mydir by calling compute_mydir in lldbtest.py. Differential Revision: https://reviews.llvm.org/D128077 | 3 年前 | |
[lldb] Copy the system debugserver in LLDB.framework When using the system debugserver for testing, copy the binary in the LLDB.framework Resource directory instead of the build's bin directory. rdar://82998263 | 4 年前 | |
Re-land "[test] Split LLDB tests into API, Shell & Unit" The original patch got reverted because it broke check-lldb on a clean build. This fixes that. llvm-svn: 374201 | 6 年前 | |
[lldb/test][Darwin] Ask dyld where the real python is Summary: On macOS, we can't do the DYLD_INSERT_LIBRARIES trick with a shim python binary as the ASan interceptors get loaded too late. Find the "real" python binary, copy it, and invoke it. Hopefully this makes the GreenDragon and swift-ci sanitizer bots happy... I tested this out by running ../llvm-macosx-x86_64/bin/llvm-lit test --filter TestNSDictionarySynthetic.py in an ASanified swift-lldb build directory and it worked (i.e. no more "interceptors loaded too late" messages). Reviewers: JDevlieghere Subscribers: lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D79607 | 6 年前 | |
[lldb] Use the just-built libc++ for testing the LLDB data formatters Make sure we use the libc++ from the build dir. Currently, by passing -stdlib=libc++, we might pick up the system libc++. This change ensures that if LLVM_LIBS_DIR is set, we try to use the libc++ from there. Differential revision: https://reviews.llvm.org/D129166 | 3 年前 | |
[lldb] Use the just-built libc++ for testing the LLDB data formatters Make sure we use the libc++ from the build dir. Currently, by passing -stdlib=libc++, we might pick up the system libc++. This change ensures that if LLVM_LIBS_DIR is set, we try to use the libc++ from there. Differential revision: https://reviews.llvm.org/D129166 | 3 年前 | |
[lldb] Parse the dotest output to determine the most appropriate result code Currently we look for keywords in the dotest.py output to determine the lit result code. This binary approach of a keyword being present works for PASS and FAIL, where having at least one test pass or fail respectively results in that exit code. Things are more complicated for tests that neither passed or failed, but report a combination of (un)expected failures, skips or unresolved tests. This patch changes the logic to parse the number of tests with a particular result from the dotest.py output. For tests that did not PASS or FAIL, we now report the lit result code for the one that occurred the most. For example, if we had a test with 3 skips and 4 expected failures, we report the test as XFAIL. We're still mapping multiple tests to one result code, so some loss of information is inevitable. Differential revision: https://reviews.llvm.org/D127258 | 3 年前 | |
[lldb/test] Use realpath consistently for test root file paths. LLDB tests assume that tests are in the test tree (the LLDB_TEST_SRC env variable, configured by dotest.py). If this assertion doesn't hold, tests fail in strange ways. An early place this goes wrong is in compute_mydir which does a simple length-based substring to get the relative path. Later, we use that path to chdir to. If the test file and test tree don't agree in realpath-ness (and therefore length), this will be a cryptic error of chdir-ing to a directory that does not exist. The actual discrepency is that the places we look for use_lldb_suite.py don't use a realpath, but dotest.py does (see initialization of configuration.testdirs). It doesn't particularly matter whether we use realpath or abspath to canonicalize things, but many places end up with implicit dependencies on the canonicalized pwd being a realpath, so make them realpath consistently. Also, in the compute_mydir method mentioned, raise an error if the path types don't agree. Reviewed By: JDevlieghere Differential Revision: https://reviews.llvm.org/D85258 | 5 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 6 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 4 年前 | ||
| 6 年前 | ||
| 6 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 5 年前 |