Cleanup LLVMDWARFDebugInfoAs usual with that header cleanup series, some implicit dependencies now need tobe explicit:llvm/DebugInfo/DWARF/DWARFContext.h no longer includes:- "llvm/DebugInfo/DW
Cleanup LLVMDWARFDebugInfoAs usual with that header cleanup series, some implicit dependencies now need tobe explicit:llvm/DebugInfo/DWARF/DWARFContext.h no longer includes:- "llvm/DebugInfo/DWARF/DWARFAcceleratorTable.h"- "llvm/DebugInfo/DWARF/DWARFCompileUnit.h"- "llvm/DebugInfo/DWARF/DWARFDebugAbbrev.h"- "llvm/DebugInfo/DWARF/DWARFDebugAranges.h"- "llvm/DebugInfo/DWARF/DWARFDebugFrame.h"- "llvm/DebugInfo/DWARF/DWARFDebugLoc.h"- "llvm/DebugInfo/DWARF/DWARFDebugMacro.h"- "llvm/DebugInfo/DWARF/DWARFGdbIndex.h"- "llvm/DebugInfo/DWARF/DWARFSection.h"- "llvm/DebugInfo/DWARF/DWARFTypeUnit.h"- "llvm/DebugInfo/DWARF/DWARFUnitIndex.h"Plus llvm/Support/Errc.h not included by a bunch of llvm/DebugInfo/DWARF/DWARF*.h filesPreprocessed lines to build llvm on my setup:after: 1065629059before: 1066621848Which is a great diff!Discourse thread: https://discourse.llvm.org/t/include-what-you-use-include-cleanupDifferential Revision: https://reviews.llvm.org/D119723
show more ...
fix lldb for recent libDebugInfoDWARF API change
[lldb] Remove custom DWARF expression printing codeThe llvm DWARFExpression dump is nearly identical, but better -- forexample it does print a spurious space after zero-argument expressions.Some
[lldb] Remove custom DWARF expression printing codeThe llvm DWARFExpression dump is nearly identical, but better -- forexample it does print a spurious space after zero-argument expressions.Some parts of our code (variable locations) have been already switchedto llvm-based expression dumping. This switches the remainder: unwindplans and some unit tests.
[lldb][NFC] Fix all formatting errors in .cpp file headersSummary:A *.cpp file header in LLDB (and in LLDB) should like this:```//===-- TestUtilities.cpp ----------------------------------------
[lldb][NFC] Fix all formatting errors in .cpp file headersSummary:A *.cpp file header in LLDB (and in LLDB) should like this:```//===-- TestUtilities.cpp -------------------------------------------------===//```However in LLDB most of our source files have arbitrary changes to this format andthese changes are spreading through LLDB as folks usually just use the existingsource files as templates for their new files (most notably the unnecessaryeditor language indicator `-*- C++ -*-` is spreading and in every reviewsomeone is pointing out that this is wrong, resulting in people pointing out that thisis done in the same way in other files).This patch removes most of these inconsistencies including the editor language indicators,all the different missing/additional '-' characters, files that center the file name, missingtrailing `===//` (mostly caused by clang-format breaking the line).Reviewers: aprantl, espindola, jfb, shafik, JDevlieghereReviewed By: JDevlieghereSubscribers: dexonsmith, wuzish, emaste, sdardis, nemanjai, kbarton, MaskRay, atanasyan, arphaman, jfb, abidh, jsji, JDevlieghere, usaxena95, lldb-commitsTags: #lldbDifferential Revision: https://reviews.llvm.org/D73258
PostfixExpression: Use signed integers in IntegerNodeSummary:This is necessary to support parsing expressions like ".cfa -16 + ^", asthat format is used in breakpad STACK CFI expressions.Since
PostfixExpression: Use signed integers in IntegerNodeSummary:This is necessary to support parsing expressions like ".cfa -16 + ^", asthat format is used in breakpad STACK CFI expressions.Since the PDB expressions use the same parser, this change will affectthem too, but I don't believe that should be a problem in practice. IfPDBs do contain the negative values, it's very likely that they areintended to be parsed the same way, and if they don't, then it doesn'tmatter.In case that we do ever need to handle this differently, we can alwaysmake the parser behavior customizable, or just use a different parser.To make sure that the integer size is big enough for everyone, I switchfrom using a (unsigned) 32-bit integer to a 64-bit (signed) one.Reviewers: amccarth, clayborg, aleksandr.urakovSubscribers: markmentovai, lldb-commitsDifferential Revision: https://reviews.llvm.org/D61311llvm-svn: 360166
Remove obsoleted NativePDB testsTheir functionality overlaps with the newly introducedPostfixExpressionTests (r359288). Tests, which still exercise somepdb-related functionality (register name re
Remove obsoleted NativePDB testsTheir functionality overlaps with the newly introducedPostfixExpressionTests (r359288). Tests, which still exercise somepdb-related functionality (register name resolution) have been kept.llvm-svn: 359450
[NFC] Fix license headers after r352845llvm-svn: 353503
[unittests] Fix warningwarning: comparison of integers of different signs: 'const int' and'const unsigned long' [-Wsign-compare]llvm-svn: 353196
[PDB] Fix location retrieval for function local variables and arguments that arestored relative to VFRAMESummary:This patch makes LLDB able to retrieve proper values for function arguments andlo
[PDB] Fix location retrieval for function local variables and arguments that arestored relative to VFRAMESummary:This patch makes LLDB able to retrieve proper values for function arguments andlocal variables stored in PDB relative to VFRAME register.Patch contains retrieval of corresponding FPO table entries from PDB and ageneric translator from FPO programs to DWARF expressions to get correct VFRAMEvalue.Patch also improves variables-locations.test and makes this test passable onx86.Patch By: leonid.mashinskyReviewers: zturner, asmith, stella.stamenova, aleksandr.urakovReviewed By: zturnerSubscribers: arphaman, labath, mgorny, aprantl, JDevlieghere, lldb-commitsTags: #lldbDifferential Revision: https://reviews.llvm.org/D55122llvm-svn: 352845