[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: MallocDebug oddities /w GNUstep on Darwin
From: |
Nicola Pero |
Subject: |
Re: MallocDebug oddities /w GNUstep on Darwin |
Date: |
Fri, 19 Jul 2002 12:08:59 +0100 (BST) |
> > #15 0x7084b3b4 in NSLog ()
> > .
> > . looped several times
> > .
> > #2146 0x7083f94c in NSLogv ()
> > #2147 0x7084b3b4 in NSLog ()
> > #2148 0x708c6660 in _NSRaiseError ()
> > #2149 0x708788b8 in -[NSException raise] ()
>
> The problem is, -[NSException raise] uses a method which might
> raise an Exception yet again -> endless loop.
Ok yes - it's a bug but ... Was the stack trace for gnustep-base or for
the Apple Foundation ?
Since there is no _NSRaiseError in gnustep, I think this stack trace is
from Apple's Foundation, and the bug is in their code, not ours.
> I told about this on March 20th on the GNUstep bug list but
> obviously neither the patch provided there nor any other
> solution made it into the sources.
>
> It would be a good idea to remove usage of NSString in
> -[NSException raise] and use fprintf() instead, IMHO. Any
> comments on this?
Looking at the gnustep-base Source, there is no NSLog in NSException - the
gnustep's _NSFoundationUncaughtExceptionHandler() is *already* using
fprintf.
So I think your remark/change/patch did make it into the gnustep-base
sources. It didn't make it into Apple's Foundation - but that's not our
problem :-)