aprantl added a comment. I understand the motivation, just a few questions about the approach:
- Can we make it such that *if* the program was compiled with -gmodules LLDB is using the DWARF module info as authoritative source instead of using this heuristic? - Is there a path towards supporting the following scenario? 1. User compiles a program that contains `@import Foo;` using a custom -DBAR define, which affects how Foo is built on the command line. 2. LLDB reads the fact the Foo was imported with -DBAR from DWARF and makes it available in the expression evaluator. Repository: rLLDB LLDB CHANGES SINCE LAST ACTION https://reviews.llvm.org/D67760/new/ https://reviews.llvm.org/D67760 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
