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: "Michael Ash" <email@hidden>
- Date: Thu, 2 Oct 2008 22:57:30 -0400
On Thu, Oct 2, 2008 at 6:24 PM, Jerry Krinock <email@hidden> wrote:
> 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.
Indeed, that should be fine. And if it weren't, you'd almost certainly
be seeing some other problem, not this particular crash.
> 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.
What's the bug, and what's the magic workaround? Also, how much code
is required to reproduce the bug, and is it small enough to post? I'm
curious as to what you've found.
Mike
_______________________________________________
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