DDavid Spickett[lldb][AArch64] Use "+all" feature for the disassembler
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
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 年前 | |
Revert "[LLDB] Handle DIE with DW_AT_low_pc and empty ranges" This reverts commit 1beededc0e7d86d09cee972f0b9f0030a139cab4. Due to failures on the Arm/AArch64 build bots: https://lab.llvm.org/buildbot/#/builders/96/builds/25032 | 3 年前 | |
Reland "[lldb] Set return status to failed when adding a command error" This reverts commit ac031c8db2ce454a9b08f23192ce698e8bde4447. SB API usage has been corrected. | 4 年前 | |
Reland "[lldb] Set return status to failed when adding a command error" This reverts commit ac031c8db2ce454a9b08f23192ce698e8bde4447. SB API usage has been corrected. | 4 年前 | |
[lldb/Commands] Make column available through _regexp-break Update _regexp-break to interpret main.c:8:21 as: breakpoint set --line 8 --column 21 Differential revision: https://reviews.llvm.org/D73314 | 6 年前 | |
[lldb][AArch64] Use "+all" feature for the disassembler The "+all" feature name was added in https://reviews.llvm.org/D128029. This feature means we don't have to generate a list of features or use a base architecture feature. Reviewed By: labath Differential Revision: https://reviews.llvm.org/D129177 | 3 年前 | |
[lldb] Fix flakiness in command-disassemble-process.yaml (2/2) I split up the test so we could stop redirecting stderr to stdout but I forgot to include that part in the previous commit. | 4 年前 | |
Refine error msgs from CommandObject & Disassemble Make it clearer for end users why a command cannot be used when a process is not stopped, etc. Differential Revision: https://reviews.llvm.org/D120594 | 4 年前 | |
Fix "image lookup --address" Summary results for inline functions. Inline callstacks were being incorrectly displayed in the results of "image lookup --address". The deepest frame wasn't displaying the line table line entry, it was always showing the inline information's call file and line on the previous frame. This is now fixed and has tests to make sure it doesn't regress. Differential Revision: https://reviews.llvm.org/D98761 | 5 年前 | |
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 年前 | |
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/lit] Introduce %clang_host substitutions Summary: This patch addresses an ambiguity in how our existing tests invoke the compiler. Roughly two thirds of our current "shell" tests invoke the compiler to build the executables for the host. However, there is also a significant number of tests which don't build a host binary (because they don't need to run it) and instead they hardcode a certain target. We also have code which adds a bunch of default arguments to the %clang substitutions. However, most of these arguments only really make sense for the host compilation. So far, this has worked mostly ok, because the arguments we were adding were not conflicting with the target-hardcoding tests (though they did provoke an occasional "argument unused" warning). However, this started to break down when we wanted to use target-hardcoding clang-cl tests (D69031) because clang-cl has a substantially different command line, and it was getting very confused by some of the arguments we were adding on non-windows hosts. This patch avoid this problem by creating separate %clang(xx,_cl)_host substutitions, which are specifically meant to be used for compiling host binaries. All funny host-specific options are moved there. To ensure that the regular %clang substitutions are not used for compiling host binaries (skipping the extra arguments) I employ a little hac^H^H^Htrick -- I add an invalid --target argument to the %clang substitution, which means that one has to use an explicit --target in order for the compilation to succeed. Reviewers: JDevlieghere, aprantl, mstorsjo, espindola Subscribers: emaste, arichardson, MaskRay, jfb, lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D69619 | 6 年前 | |
[lldb/Driver] Exit with a non-zero exit code in case of error in batch mode. We have the option to stop running commands in batch mode when an error occurs. When that happens we should exit the driver with a non-zero exit code. Differential revision: https://reviews.llvm.org/D78825 | 6 年前 | |
[lldb] Prevent crash when adding a stop hook with --shlib Currently, lldb crashes when adding a stop hook with --shlib because we unconditionally use the target in SymbolContextSpecifier::AddSpecification. This patch prevents the crash and add a test. rdar://68524781 Differential revision: https://reviews.llvm.org/D123746 | 4 年前 | |
Revert "Revert "Add the ability to write target stop-hooks using the ScriptInterpreter."" This reverts commit f775fe59640a2e837ad059a8f40e26989d4f9831. I fixed a return type error in the original patch that was causing a test failure. Also added a REQUIRES: python to the shell test so we'll skip this for people who build lldb w/o Python. Also added another test for the error printing. | 5 年前 | |
[lldb] Second attempt at fixing command-target-create-resolve-exe.test on the buildbot | 3 年前 | |
[test] Replace yaml2obj > with yaml2obj -o and remove unneeded input redirection | 5 年前 | |
[lldb] Make sure we don't drop asynchronous output when sourcing files Summary: If a command from a sourced file produces asynchronous output, this output often does not make its way to the user. This happens because the asynchronous output machinery relies on the iohandler stack to ensure the output does not interfere with the things the iohandler is doing. However, if this happens near the end of the command stream then by the time the asynchronous output is produced we may already have already started tearing down the sourcing session. Specifically, we may already pop the relevant iohandler, leaving the stack empty. This patch makes sure this kind of output gets printed by adding a fallback to IOHandlerStack::PrintAsync to print the output directly if the stack is empty. This is safe because if we have no iohandlers then there is nothing to synchronize. Reviewers: JDevlieghere, clayborg Subscribers: lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D75454 | 6 年前 | |
[lldb] Require native for command-thread-siginfo.test command-thread-siginfo.test employs a subject with a call to wait, and thus requires system-linux. However, it's possible to target non-Linux platforms despite operating on Linux hosts. So, have it require native too. Reviewed By: mgorny, labath Differential Revision: https://reviews.llvm.org/D121487 | 4 年前 | |
[lldb] Second attempt at fixing command-target-create-resolve-exe.test on the buildbot | 3 年前 |