On 1 December 2017 at 19:42, Jim Ingham <jing...@apple.com> wrote: > This certainly should be cleared up and centralized. I'm not quite as sure > it should be in Platform however. For instance, macOS has the DebugSymbols > framework that allows users to specify a local lookup tool to find symbol > files given a UUID. That runs only on MacOS and requires MacOS specific > headers to build. So that makes it a Host facility. But there's no reason > you couldn't use this mechanism for finding Linux symbol files when cross > debugging. So that makes it sound more like this Platform symbol finding > facility you're envisioning. I'm still a little unclear about the > distinction between Host, Platform when the platform isn't the same as the > Host, and Platform when it happens to be the same as the Host. > > But maybe this is clear and I just haven't studied the more recent > manifestations of the code recently.
I agree that the host/platform split is not very clear currently. We'll need to think about it when the time comes. Maybe we just need to peel off one layer from the Host here and move it somewhere. For example the concrete details of how to invoke the DebugSymbols framework can stay in Host (roughly the LocateMacOSXFilesUsingDebugSymbols function, I guess), but then all the smartness about what to do with it can live somewhere else. _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
