Project Ortega BCM5719 LLVM https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1 2020-01-14T14:19:29+00:00 2020-01-14T14:19:29+00:00 Pavel Labath pavel@labath.sk 2019-12-23T15:31:36+00:00 urn:sha1:4b5bc38802dcc7d2c6d7f5af1eca1755bd0fd9cb These are the last sections not managed by the DWARFContext object. I also introduce separate SectionType enums for dwo section variants, as this is necessary for proper handling of single-file split dwarf. 2020-01-14T13:59:56+00:00 Levon Ter-Grigoryan patriosthegreat@protonmail.ch 2020-01-14T13:33:43+00:00 urn:sha1:a705cf1acbe94498f7fcca4e89be6d4820271227 Summary: This change is connected with https://reviews.llvm.org/D69843 In large codebases, we sometimes see Module::FindFunctions (when called from ClangExpressionDeclMap::FindExternalVisibleDecls) returning huge amounts of functions. In current fix I trying to return only function_fullnames from ManualDWARFIndex::GetFunctions when eFunctionNameTypeFull is passed as argument. Reviewers: labath, jarin, aprantl Reviewed By: labath Subscribers: shafik, clayborg, teemperor, arphaman, lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D70846 2020-01-09T12:19:29+00:00 Pavel Labath pavel@labath.sk 2019-12-20T08:42:37+00:00 urn:sha1:cd5da94d80b2b0f2bdb2d0157e24705a4cbd2a4e Summary: Our code was expecting that a single (symbol) file contains only one kind of location lists. This is not correct (on non-apple platforms, at least) as a file can compile units with different dwarf versions. This patch moves the deteremination of location list flavour down to the compile unit level, fixing this problem. I have also tried to rougly align the code with the llvm DWARFUnit. Fully matching the API is not possible because of how lldb's DWARFExpression lives separately from the rest of the DWARF code, but this is at least a step in the right direction. Reviewers: JDevlieghere, aprantl, clayborg Subscribers: dblaikie, lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D71751 2019-12-23T13:54:22+00:00 Pavel Labath pavel@labath.sk 2019-12-23T13:33:00+00:00 urn:sha1:46f02fc922e053006e34d860e9efaf29c88d8ba3 This bit of code is trying to strip everything up to the first colon from all debug info paths, as dwarf2 recommends this syntax for storing the compilation host name. However, this code was too eager, and it ended up stripping the entire compilation directory, if it did not contain a forward slash (or a "x:\"). Normally this does not matter, as all absolute paths will contain one of these patterns, but this does not have to be the case in case the debug info is produced by "clang -fdebug-compilation-dir", which can end up producing a relative compilation directory with no slashes (this is one of the techniques for producing "relocatable" debug info). 2019-12-21T05:11:50+00:00 Jonas Devlieghere jonas@devlieghere.com 2019-12-21T05:10:20+00:00 urn:sha1:3fa39c3a79a3b1a88d2da0b3992089e9134fb87f The isysroot field in DIModule was renamed to sysroot but the test in LLDB wasn't updated. This fixes that. 2019-12-20T12:27:40+00:00 Johannes Altmanninger aclopte@gmail.com 2019-12-20T12:25:27+00:00 urn:sha1:04329dbfa6c219997ab72567842d81778f9f7f47 2019-12-20T08:04:45+00:00 Johannes Altmanninger aclopte@gmail.com 2019-11-27T21:48:15+00:00 urn:sha1:92211bf0f15ba46b5eeb88b7ea580ff539dcdd4e Summary: Fixes PR41237 - SIGSEGV on call expression evaluation when debugging clang When linking multiple compilation units that define the same functions, the functions is merged but their debug info is not. This ignores debug info entries for functions in a non-executable sections; those are functions that were definitely dropped by the linker. Reviewers: spyffe, clayborg, jasonmolenda Reviewed By: clayborg Subscribers: labath, aprantl, lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D71487 2019-12-12T14:28:11+00:00 Pavel Labath pavel@labath.sk 2019-11-25T13:03:51+00:00 urn:sha1:6ce1a897b6a82e18059fd3b75b8d52ff12c2a605 Dwo files don't have a DW_AT_loclists_base -- set one explicitly. Also, make sure we use the correct location list flavour for v5. 2019-12-12T10:45:03+00:00 Pavel Labath pavel@labath.sk 2019-12-09T17:24:45+00:00 urn:sha1:d6d36ae4a052e9fefd2926005a69f6cebfa5832b Summary: This enables us to display the contents of atomic structs. Calling the removal of _Atomic "desugaring" is not fully correct as it does more than remove sugar, but it is the right thing to do for most of the things that we care about. We can change this back once we decide to support atomic types more comprehensively. Reviewers: teemperor, shafik Subscribers: jfb, lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D71262 2019-12-11T10:06:17+00:00 Pavel Labath pavel@labath.sk 2019-11-22T13:42:28+00:00 urn:sha1:c8b74ee264a943aad29fd0864c610ba5504f73a8 Summary: This adds support for DWARF5 location lists which are specified indirectly, via an index into the debug_loclists offset table. This includes parsing the DW_AT_loclists_base attribute which determines the location of this offset table, and support for new form DW_FORM_loclistx which is used in conjuction with DW_AT_location to refer to the location lists in this way. The code uses the llvm class to parse the offset information, and I've also tried to structure it similarly to how the relevant llvm functionality works. Reviewers: JDevlieghere, aprantl, clayborg Subscribers: lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D71268