Re: -[NSScanner scanUpToString:stopString:NULL] - 10.3.9 Crash, due Xcode 3.1?
Re: -[NSScanner scanUpToString:stopString:NULL] - 10.3.9 Crash, due Xcode 3.1?
- Subject: Re: -[NSScanner scanUpToString:stopString:NULL] - 10.3.9 Crash, due Xcode 3.1?
- From: Jerry Krinock <email@hidden>
- Date: Fri, 3 Oct 2008 11:34:14 -0700
As far as I can see, this is another symptom of a bug which I found
back in March 2008 in Mac OS 10.3.
The bug is that when an application is run in Mac OS 10.3.9, it
crashes when a method in an NSScanner category that is defined in a
framework does a simple scan. It runs fine in Mac OS 10.5, and
indications are, 10.4.
Back in March 2008, I found that this only happened if it was the
first code to execute in the application executable, and a workaround
was to execute one line of "regular" code before invoking the category
in the framework. But after updating from Xcode 3.0 to Xcode 3.1.1,
this no longer works. I tried playing around with some of the build
settings in the framework for awhile, but none of what I tried fixed it.
Also back in March 2008, I thought that this affected other classes in
addition to NSScanner.
Discussion of the March 2008 issue is here:
http://www.cocoabuilder.com/archive/message/cocoa/2008/3/27/202404
Here is the demo project in case anyone is interested.
http://sheepsystems.com/engineering/PantherCrasher.zip (46 KB)
My solution is to tell Mac OS 10.3.9 users that they are not getting
any more updates, and then I'll have to make the old version available
"manually" when they need it. Kind of a pain, but not as painful as
keeping an Xcode 3.0 around.
_______________________________________________
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