Re: Problems with Universal Build...
Re: Problems with Universal Build...
- Subject: Re: Problems with Universal Build...
- From: Ricky Sharp <email@hidden>
- Date: Sun, 23 Dec 2007 20:38:22 -0600
On Dec 23, 2007, at 8:13 PM, Jerry LeVan wrote:
You are right about the first two questions, checking the console I
find that the
following error appears immediately after the attempt to write the pdf
2007-12-23 20:12:35.052 ImageBrowser[2490] *** -[NSCFNumber
isLocked]: selector not recognized [self = 0x3efd00]
2007-12-23 20:12:35.053 ImageBrowser[2490] *** -[NSCFNumber
isLocked]: selector not recognized [self = 0x3efd00]
Since it works fine on Intel I am suspecting an error somewhere in
the ppc libraries...
Why would you say that? If you look at what's given in the console,
you'll see that an instance of NSNumber/CFNumber is being sent the
isLocked message. Looking up isLocked in the docs reveals that it's a
message that can be sent to instances of PDFDocument.
Thus, I believe your app is trashing memory since you're working with
the PDF API and somehow what used to be a PDFDocument instance is now
something else.
Run your app with the various memory-debugging stuff (e.g. zombies,
malloc scribble, etc.)
___________________________________________________________
Ricky A. Sharp mailto:email@hidden
Instant Interactive(tm) http://www.instantinteractive.com
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden