Re: How to allow users of pre-built libraries step into code in the Xcode debugger?
Re: How to allow users of pre-built libraries step into code in the Xcode debugger?
- Subject: Re: How to allow users of pre-built libraries step into code in the Xcode debugger?
- From: Eric Wing <email@hidden>
- Date: Wed, 13 May 2015 17:04:03 -0700
On 5/13/15, email@hidden <email@hidden> wrote:
> When you build a library, the location of the source files is written into
> the debug information which is stored in the dSYM. When you are in the
> debugger and stop in some code from that library, lldb uses the debug info
> to figure out where you have stopped, and load the source for that location.
> The debug information tells it the location on the build machine, but
> there's nothing to tell us where the sources are on the debugging machine.
> You have to do that by hand.
>
> The way to do that in lldb is to set the "target.source-map" setting. So
> for instance, if on the builder your project was in
> /Volumes/Builder/Sources, and on the users machine the sources are in
> /Volumes/TheirDisk/Sources, you would say:
>
> (lldb) settings set target.source-map /Volumes/Builder/Sources
> /Volumes/TheirDisk/Sources
>
> Then lldb will take any source file that claims to be under the original
> hierarchy, and look for it under the new hierarchy instead.
>
> If you don't know the original build directory, just do:
>
> (lldb) image lookup -vn <SomeFunctionInTheLibrary>
>
> and one of the output lines will be the CompileUnit. That will show the
> path to the source file that was in the DWARF. This generally isn't at the
> top level of the build hierarchy, so you'll need to go back a couple of
> directories. You can generally tell what the common base is from looking at
> the sources you've downloaded.
>
> Jim
>
That is very useful information. Thank you!
A couple of follow up questions.
- I actually have a dozen or so libraries. Is it possible to set
multiple maps at the same time if they don't share a common root?
- I noticed that Xcode is not remembering what I set between runs. The
lldb up-arrow history helps, but is there a way to make this a little
more persistent?
- Or maybe, is there a way I could use something like awk/sed/Perl to
rewrite the paths for the user's copies of the .dSYM and .a files so
re-entering in lldb isn't required every single time?
Thanks,
Eric
--
Beginning iPhone Games Development
http://playcontrol.net/iphonegamebook/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden