en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/functionalities/limit-debug-info/Makefile#d6343e60 [lldb] Skip TestLimitDebugInfo on windowsThe test does not work on windows, because clang will emit full typeinformation for __declspec(dllexport) types even under-flimit-debug-info. __declspec(dllexport) is needed to be able to usethe type across shared library boundaries on windows, which makes this apretty good heuristic, but defeats the purpose of this test.I am going to create (in another patch) an basic assembly test, so thatthe relevant code gets at least some coverage on windows hosts.This also reverts commit 1276855f2b4485ec312b379c1b8eaf5510d9b157, whichadded the __declspec annotations -- they are not necessary anymore, andthey needlessly complicate the test. List of files: /llvm-project-15.0.7/lldb/test/API/functionalities/limit-debug-info/Makefile Thu, 02 Jul 2020 12:28:03 +0000 Pavel Labath <pavel@labath.sk> http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/functionalities/limit-debug-info/Makefile#1276855f [lldb] Attempt to fix TestLimitDebugInfo on windowsThe test fails due to link errors. I believe this change should fixthat. List of files: /llvm-project-15.0.7/lldb/test/API/functionalities/limit-debug-info/Makefile Wed, 01 Jul 2020 14:55:34 +0000 Pavel Labath <pavel@labath.sk> http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/functionalities/limit-debug-info/Makefile#a03dc8c9 [lldb] Add basic -flimit-debug-info support to expression evaluatorSummary:This patch adds support for evaluation of expressions referring to typeswhich were compiled in -flimit-debug-info (a.k.a -fno-standalone-debug)in clang. In this mode it's possible that the debug information neededto fully describe a c++ type is not present in a single shared library-- for example debug info for a base class or a member of a type canonly be found in another shared library. This situation is notcurrently handled well within lldb as we are limited to searching withina single shared library (lldb_private::Module) when searching for thedefinition of these types.The way that this patch gets around this limitation is by doing thesearch at a later stage -- during the construction of the expression astcontext. This works by having the parser (currently SymbolFileDWARF, buta similar approach is probably needed for PDBs too) mark a type as"forcefully completed". What this means is that the parser has markedthe type as "complete" in the module ast context (as this is necessaryto e.g. derive classes from it), but its definition is not really there.This is done via a new field on the ClangASTMetadata struct.Later, when we are importing such a type into the expression ast, wecheck this flag. If the flag is set, we try to find a better definitionfor the type in other shared libraries. We do this by initiating anew lookup for the "forcefully completed" classes, which then imports thetype from a module with a full definition.This patch only implements this handling for base classes, but othercases (members, array element types, etc.). The changes for that shouldbe fairly simple and mostly revolve around marking these types as"forcefully completed" at an approriate time -- the importing logic isgeneric already.Another aspect, which is also not handled by this patch is viewing thesetypes via the "frame variable" command. This does not use the ASTimporter and so it will need to handle these types on its own -- thatwill be the subject of another patch.Differential Revision: https://reviews.llvm.org/D81561 List of files: /llvm-project-15.0.7/lldb/test/API/functionalities/limit-debug-info/Makefile Tue, 23 Jun 2020 09:34:58 +0000 Pavel Labath <pavel@labath.sk>