PPavel Labath[lldb] Fix collisions between two breakpad tests
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[LLDB][Breakpad] Make lldb understand INLINE and INLINE_ORIGIN records in breakpad. Teach LLDB to understand INLINE and INLINE_ORIGIN records in breakpad. They have the following formats: INLINE inline_nest_level call_site_line call_site_file_num origin_num [address size]+ INLINE_ORIGIN origin_num name INLNIE_ORIGIN is simply a string pool for INLINE so that we won't have duplicated names for inlined functions and can show up anywhere in the symbol file. INLINE follows immediately after FUNC represents the ranges of momery address that has functions inlined inside the function. Differential Revision: https://reviews.llvm.org/D113330 | 4 年前 | |
Fix inline-record.test for Arm/Windows This patch fixes inline-record.test to run on multiple platforms including Arm/Windows. Test is fixed to expect any value for id fields of functions and blocks returned by 'image lookup' command. This field can be any value as it is internally generated id. | 4 年前 | |
[test] Replace yaml2obj > with yaml2obj -o and remove unneeded input redirection | 5 年前 | |
[test] Replace yaml2obj > with yaml2obj -o and remove unneeded input redirection | 5 年前 | |
[test] Replace yaml2obj > with yaml2obj -o and remove unneeded input redirection | 5 年前 | |
[test] Replace yaml2obj > with yaml2obj -o and remove unneeded input redirection | 5 年前 | |
[LLDB][Breakpad] Create a function for each compilation unit. Since every FUNC record (in breakpad) is a compilation unit, creating the function for the CU allows ResolveSymbolContext to resolve eSymbolContextFunction. Differential Revision: https://reviews.llvm.org/D113163 | 4 年前 | |
[lldb] add lit.local.cfg for breakpad tests The reason is to add .yaml as a valid test suffix. The test folder contains one yaml file, which wasn't being run because of that. Unsurprisingly the test fails, but this was not because the underlying functionality was broken, but rather because the test was setup incorrectly (most likely due to overly aggressive simplification of the test data on my part). Therefore this patch also tweaks the test inputs in order to test what they are supposed to test, and also updates some other breakpad tests (because they depend on the same inputs as this one) to be more realistic -- specifically it avoids putting symbols to the first page of the module, as that's where normally the COFF header would reside. | 6 年前 | |
[test] Replace yaml2obj > with yaml2obj -o and remove unneeded input redirection | 5 年前 | |
Update UnwindPlan dump to list if it is a trap handler func; also Command Update the "image show-unwind" command output to show if the function being shown is listed as a user-setting or platform trap handler. Update the individual UnwindPlan dumps to show whether the unwind plan is registered as a trap handler. | 5 年前 | |
[test] Replace yaml2obj > with yaml2obj -o and remove unneeded input redirection | 5 年前 | |
[lldb] Fix collisions between two breakpad tests symtab-sorted-by-size.test was using the same output file name as symtab.test. | 2 年前 | |
[LLDB][Breakpad] Create a function for each compilation unit. Since every FUNC record (in breakpad) is a compilation unit, creating the function for the CU allows ResolveSymbolContext to resolve eSymbolContextFunction. Differential Revision: https://reviews.llvm.org/D113163 | 4 年前 | |
[lldb] Require x86 for various NativePDB, Breakpad and Minidump tests These tests fail if you build without the x86 llvm backend. Either because they use an x86 triple or try to backtrace which requires some x86 knowledge to see all frames. Reviewed By: labath Differential Revision: https://reviews.llvm.org/D100194 | 5 年前 | |
Update UnwindPlan dump to list if it is a trap handler func; also Command Update the "image show-unwind" command output to show if the function being shown is listed as a user-setting or platform trap handler. Update the individual UnwindPlan dumps to show whether the unwind plan is registered as a trap handler. | 5 年前 | |
[LLDB][Minidump] Merge executable module's architecture into target's architecture. This allows minidump process ABI to match the PE/COFF file ABI. Reviewed By: labath Differential Revision: https://reviews.llvm.org/D137873 | 3 年前 | |
Update UnwindPlan dump to list if it is a trap handler func; also Command Update the "image show-unwind" command output to show if the function being shown is listed as a user-setting or platform trap handler. Update the individual UnwindPlan dumps to show whether the unwind plan is registered as a trap handler. | 5 年前 |