jingham added a subscriber: jingham. jingham added a comment. This approach seems fragile to me. I'm supposed to remember that some build system set some rewriter file that I then have to supply manually to get the view of symbols to match reality? We really try to avoid having to write notes on little pieces of paper and typing them back in to get debugging to work...
This should get recorded somewhere in the module that uses it, and then the module reader code would be able to find and apply it automatically. If this is passed to the compiler, it should get written into the DWARF. But it sounds more like it gets passed to then linker. So maybe we can stick this map file in a load command, or symbol that the symbol file reader can fetch. You might need a command to give search paths for these remap files in case you move the around, but that's all that the user should need to do by hand. http://reviews.llvm.org/D22294 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
