[lldb] Add gnu-debuglink support for Windows PE/COFFThe specification of gnu-debuglink can be found at:https://sourceware.org/gdb/onlinedocs/gdb/Separate-Debug-Files.htmlThe file CRC or the CRC
[lldb] Add gnu-debuglink support for Windows PE/COFFThe specification of gnu-debuglink can be found at:https://sourceware.org/gdb/onlinedocs/gdb/Separate-Debug-Files.htmlThe file CRC or the CRC value from the .gnu_debuglink section is nowused to calculate the module UUID as a fallback, to allow verifying thatthe debug object does match the executable. Note that if a CodeViewbuild id exists, it still takes precedence. This works even for MinGWbuilds because LLD writes a synthetic CodeView build id which does notget stripped from the debug object.The `Minidump/Windows/find-module` test also needs a fix by adding aCodeView record to the exe to match the one in the minidump, otherwiseit fails due to the new UUID calculated from the file CRC.Fixes https://github.com/llvm/llvm-project/issues/54344Reviewed By: DavidSpickettDifferential Revision: https://reviews.llvm.org/D126367
show more ...
[lldb] Require x86 for various NativePDB, Breakpad and Minidump testsThese tests fail if you build without the x86 llvm backend.Either because they use an x86 triple or try to backtrace whichrequ
[lldb] Require x86 for various NativePDB, Breakpad and Minidump testsThese tests fail if you build without the x86 llvm backend.Either because they use an x86 triple or try to backtrace whichrequires some x86 knowledge to see all frames.Reviewed By: labathDifferential Revision: https://reviews.llvm.org/D100194
Update UnwindPlan dump to list if it is a trap handler func; also CommandUpdate the "image show-unwind" command output to show if the functionbeing shown is listed as a user-setting or platform tr
Update UnwindPlan dump to list if it is a trap handler func; also CommandUpdate the "image show-unwind" command output to show if the functionbeing shown is listed as a user-setting or platform trap handler.Update the individual UnwindPlan dumps to show whether the unwind planis registered as a trap handler.
[test] Replace `yaml2obj >` with `yaml2obj -o` and remove unneeded input redirection
[LLDB] [ARM] Use r11 as frame pointer on Windows on ARMExtend EmulateMOVRdRm to identify "mov r11, sp" in thumb mode assetting the frame pointer, if r11 is the frame pointer register.Differentia
[LLDB] [ARM] Use r11 as frame pointer on Windows on ARMExtend EmulateMOVRdRm to identify "mov r11, sp" in thumb mode assetting the frame pointer, if r11 is the frame pointer register.Differential Revision: https://reviews.llvm.org/D70797
[LLDB] [PECOFF] Don't crash in ReadImageDataByRVA for addresses out of rangeThis can happen e.g. when unwinding doesn't work perfectly.Differential Revision: https://reviews.llvm.org/D69502
Re-land "[test] Split LLDB tests into API, Shell & Unit"The original patch got reverted because it broke `check-lldb` on a cleanbuild. This fixes that.llvm-svn: 374201
Revert [test] Split LLDB tests into API, Shell & Unitas it appears to have broken check-lldb.This reverts r374184 (git commit 22314179f0660c172514b397060fd8f34b586e82)llvm-svn: 374187
[test] Split LLDB tests into API, Shell & UnitLLDB has three major testing strategies: unit tests, tests that exercisethe SB API though dotest.py and what we currently call lit tests. Thelater is
[test] Split LLDB tests into API, Shell & UnitLLDB has three major testing strategies: unit tests, tests that exercisethe SB API though dotest.py and what we currently call lit tests. Thelater is rather confusing as we're now using lit as the driver for allthree types of tests. As most of this grew organically, the directorystructure in the LLDB repository doesn't really make this clear.The 'lit' tests are part of the root and among these tests there's aUnit and Suite folder for the unit and dotest-tests. This layout makesit impossible to run just the lit tests.This patch changes the directory layout to match the 3 testingstrategies, each with their own directory and their own configurationfile. This means there are now 3 directories under lit with 3corresponding targets: - API (check-lldb-api): Test exercising the SB API. - Shell (check-lldb-shell): Test exercising command line utilities. - Unit (check-lldb-unit): Unit tests.Finally, there's still the `check-lldb` target that runs all three testsuites.Finally, this also renames the lit folder to `test` to match the LLVMrepository layout.Differential revision: https://reviews.llvm.org/D68606llvm-svn: 374184