We require a workaround to be able to locate global and anonymous namespace functions in the dwarf symbols on linux binaries. This patch enables this code on all platforms so that we can still find these symbols when debugging from a different host platform.
Details
- Reviewers
clayborg - Commits
- rG5cbd3bfca136: Enable workaround for finding functions in global namespace on linux binaries…
rLLDB237270: Enable workaround for finding functions in global namespace on linux binaries on
rL237270: Enable workaround for finding functions in global namespace on linux binaries on
Diff Detail
- Repository
- rL LLVM
Event Timeline
lldb/trunk/source/Plugins/SymbolFile/DWARF/SymbolFileDWARF.cpp | ||
---|---|---|
4054–4055 | This check is only meaningful under a particular ABI. Could you check the triple or ArchSpec of the target you're looking at first, and either not do this if the triple contains MSVC (or better yet, add a correct check)? |
lldb/trunk/source/Plugins/SymbolFile/DWARF/SymbolFileDWARF.cpp | ||
---|---|---|
4054–4055 | Hey, I added a check that the object file is linux or freebsd: http://reviews.llvm.org/D9782. I tried to add a check for windows arch as well, but the arch was not correctly recognized in my tests, I was seeing i386-unknown-unknown. Let me know if you know where I might be able to find the target arch instead if not through the object file and I'm happy to add a correct Windows check as well. Thanks. |
If it's not correct in the object file I think the best fix is to make it
correct in the object file. I actually had to fix a few things like that
in the past. Either way, don't worry about it. I will get around to it
eventually :) Maybe a comment saying // TODO: The arch in the object file
isn't correct for MSVC binaries on windows, so we should find a way to make
it correct.
This check is only meaningful under a particular ABI. Could you check the triple or ArchSpec of the target you're looking at first, and either not do this if the triple contains MSVC (or better yet, add a correct check)?