Getting the deployment target can be significant information when rebuilding clang modules since availability information could depend on it. The unittest is cargo-culted from the ELF unit tests.
rdar://problem/40039633
Paths
| Differential D46669
Retrieve the deployment target when retrieving an object file's triple ClosedPublic Authored by aprantl on May 9 2018, 6:11 PM.
Details Summary Getting the deployment target can be significant information when rebuilding clang modules since availability information could depend on it. The unittest is cargo-culted from the ELF unit tests. rdar://problem/40039633
Diff Detail
Event TimelineComment Actions The test you copied this from predates lldb-test (and it tests some behavior quirks which are not nicely expressible in text output). We should have nicer ways of testing things like this now. It should be sufficient to add a print line which displays the triple in the dumpModules function in lldb-test.cpp. Then you can just run lldb-test module-sections your-file and FileCheck that. The other thing you will need to do is make this test darwin-only as right now our MachO parsing code does not work on non-apple platforms. The reason for that is very silly - ObjectFileMachO depends on RegisterContextDarwin_XXX (presumably to read register information from core files), which use constants like KERN_SUCCESS from system headers. (I've looked at this recently because I wanted to make some cross-platform tests for apple debug info and got stuck here.) This revision is now accepted and ready to land.May 10 2018, 5:41 PM Closed by commit rL332067: Retrieve the deployment target when retrieving an object file's triple. (authored by adrian). · Explain WhyMay 10 2018, 5:44 PM This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 146264 lldb/trunk/lit/Modules/lc_version_min.yaml
lldb/trunk/source/Plugins/ObjectFile/Mach-O/ObjectFileMachO.cpp
|