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: Thu, 2 Oct 2008 15:24:16 -0700
On 2008 Oct, 02, at 4:54, Karan, Cem (Civ, ARL/CISD) wrote:
I'm coming into this late, but are you positive you never
accidentally pass in NULL like so:?
[blah scanUpToAndThenLeapOverString:@"someString" intoString:NULL];
Well, Cem actually I am passing it NULL, which then gets passed as the
second argument to -[NSScanner scanUpToString:intoString], but
according to the documentation NULL is OK there, and I've been doing
it for years.
News Flash: I've reproduced the problem in a small demo app. Looks
like the same bug in 10.3 that I found back in March (CLANG!!), but
the inexplicably magic workaround which I applied back then has
stopped working.
Will post resolution when it's done.
Thanks for your thoughts,
Jerry
_______________________________________________
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