Re: Debugging a static library
Re: Debugging a static library
- Subject: Re: Debugging a static library
- From: Todd <email@hidden>
- Date: Sun, 30 Oct 2011 14:43:48 -0700
Hi Jens,
On Sun, Oct 30, 2011 at 1:38 PM, Jens Alfke
<email@hidden> wrote:
On Oct 30, 2011, at 12:39 PM, Todd wrote:
> • I have built the shared library with Debug symbols
> • I have placed a break-point in the shared library .cpp file where I should enter but Xcode does not stop at it.
I _think_ this is supposed to work, as long as the library is built with symbols and the source files are still available at the same paths.
If it doesn’t, the next thing I would try is adding the project that builds the library to your application’s project/workspace.
I tried this and no change.
> • I have tried placing NSLog statements in the shared library and building it again to see if they show up in the console and I dont see where they do before the crash.
That’s a pretty strong indication that those statements aren’t reached. If they were they’d show up in the console output. So either
(a) your intuition about what code is being called is wrong for some reason; or
(b) the linker isn’t linking the copy of the library you built, but some other copy of it.
I tried running `otool -L` and `nm` and I get:
jtsm$ nm Mystical-Universal.app
nm: can't map file: Mystical-Universal.app (Invalid argument)
jtsm$ otool -L Mystical-Universal
otool: can't open file: Mystical-Universal (No such file or directory)
-Jason
_______________________________________________
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