Re: Printing crash
Re: Printing crash
- Subject: Re: Printing crash
- From: Daniel Jalkut <email@hidden>
- Date: Tue, 13 Feb 2007 12:04:10 -0500
Do they also happen when simply trying to load the affected plugin? I
think you should focus on that instead of printing, because it's a
simpler test case. In fact, I'd test loading that bundle manually as
early as possible in your app, to see if there's a point at which
loading it is safe.
I don't agree with the theory that EXC_BAD_ACCESS is a "clear
indication that you have a memory management problem." Lots of
things could be going wrong here, and to me it sounds like you're
chasing red herring.
You've got a simple crashing test case in 2 lines of code, now it's
just down to figuring out when and why those 2 lines of code will
cause a crash.
Daniel
On Feb 13, 2007, at 2:41 AM, Jeff Hellman wrote:
Ok...so when I got this all working, I think, I wind up with these two
outputs to the run log when trying to print:
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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