On Fri, Oct 3, 2008 at 2:34 PM, Jerry Krinock <[EMAIL PROTECTED]> wrote:
> 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 th
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
On Thu, Oct 2, 2008 at 6:24 PM, Jerry Krinock <[EMAIL PROTECTED]> 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.
In
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 pas
>Yes, I see what you mean there. It looks suspicious without the rest
>of the code. Here is the entire method (without the logging)
>
>- (BOOL)scanUpToAndThenLeapOverString:(NSString*)stopString
>intoString:(NSString**)stringValue {
> [self scanUpToString:stopStr
On Wed, Oct 1, 2008 at 8:11 PM, Jerry Krinock <[EMAIL PROTECTED]> wrote:
>
> On 2008 Oct, 01, at 15:17, Michael Ash wrote:
>
>> Without seeing the rest of your code I can't say for sure, but this is
>> extremely suspect
>>
>> You should essentially always use this method (and any other method
>
On 2008 Oct, 01, at 15:17, Michael Ash wrote:
Without seeing the rest of your code I can't say for sure, but this is
extremely suspect
You should essentially always use this method (and any other method
that uses a SomeClass** parameter to "return" values) like this:
NSString *stringValue
On Wed, Oct 1, 2008 at 3:57 PM, Jerry Krinock <[EMAIL PROTECTED]> wrote:
> After updating from Xcode 3.0 to 3.1.1, my project crashes repeatably in
> 10.3.9, while loading the (old) Sparkle 1.1 framework, and in a couple other
> places.
>
> (Yes, I'm just about to cut my two or remaining Panther us
After updating from Xcode 3.0 to 3.1.1, my project crashes repeatably
in 10.3.9, while loading the (old) Sparkle 1.1 framework, and in a
couple other places.
(Yes, I'm just about to cut my two or remaining Panther users loose
and send them an old version. But I always try and fix these thi
