When you build a static library that includes DWARF information, you may encounter error messages in the binary package generated by Xcodebuild. Upon examining the DWARF information with dwarfdump, you will find that any entries containing keywords like dir are all absolute paths specific to the publisher's computer.
This is quite alarming, as it poses a risk of leaking private information. Additionally, when debugging an app, you can encounter consistent warning notes indicating that the referenced path addresses cannot be found. This is because the absolute path addresses generated during the 'xcodebuild' process reflect the paths from the computer used to build it. When distributing this to others, how can anyone access these paths?
Has the design of the secondary linking process for DWARF considered the issues related to binary distribution?
- Are there existing solutions to address and handle privacy concerns?
- Is there a solution to allow the distributed DWARF files to be correctly recognized during compilation and debugging of the app?
BTW: Incorrect paths can indeed affect LLDB's ability to load and debug the application effectively?
