Re: Debugging a static library
Re: Debugging a static library
- Subject: Re: Debugging a static library
- From: Geoff Beier <email@hidden>
- Date: Sun, 30 Oct 2011 18:18:14 -0400
On Sun, Oct 30, 2011 at 17:43, Todd <email@hidden> wrote:
> On Sun, Oct 30, 2011 at 1:38 PM, Jens Alfke <email@hidden> wrote:
>> 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)
It's certain that neither of those commands (assuming you executed
them from the same location) is useful. Mystical-Universal.app is
pretty well certainly a bundle. Try looking at the otool output for
Mystical-Universal.app/Contents/MacOS/Mystical-Universal or whatever
is appropriate for your package. otool expects to be run on the actual
binary, not the bundle.
HTH,
Geoff
_______________________________________________
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