Re: Re-associating source files in Instruments
Re: Re-associating source files in Instruments
- Subject: Re: Re-associating source files in Instruments
- From: "Sean McBride" <email@hidden>
- Date: Mon, 20 Sep 2010 16:14:35 -0400
- Organization: Rogue Research Inc.
On Mon, 20 Sep 2010 08:48:53 +0100, Matt Gough said:
>The production builds of our product are done on a different Mac to the
>normal development builds, and I have no access to this Mac.
>
>Whenever I get an Instruments trace from a production build, I can't see
>the source code when double-clicking an individual sample. I am guessing
>that this is because the file paths of the source files do not match my
>local ones.
>
>Is there a way to get Instruments to use a different source tree from
>the one that the binaries were built against? Something akin to Shark's
>"Source Paths" preference.
I have asked a similar question in the past, and no one seems to know. :(
In my case, Instruments often fails to find source even when everything
is built on my machine and all in debug. Shark can show source for the
same executable.
There is File > Re-symbolicate Document, but it seems to always be disabled.
You might try dragging your source file into the view that should show
source (but shows assembly). That might work. Though in my case in
generally crashes.
Good luck,
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
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