Hi,
There's a bug in KVC.
When constructing setValue:forKey: method name, the method in has garbage at the end
(after the ':').
In NSKeyValueCoding.m, I think there should be a
buf[size+5] = '\0';
after each
buf[size+4] = ':';
BTW, is it possible to use strncpy instead of strcpy
On Wednesday, February 27, 2002, at 08:46 AM, Manuel Guesdon wrote:
> Hi,
>
> There's a bug in KVC.
> When constructing setValue:forKey: method name, the method in has
> garbage at the end (after the ':').
> In NSKeyValueCoding.m, I think there should be a
> buf[size+5] = '\0';
> after ea
On Wednesday, February 27, 2002, at 12:12 AM, Enrico Sersale wrote:
>
> With the latest cvs snapshot (ten minutes ago) all the apps crash.
> Reverting to the yesterday's base sources the problem disappears.
Should be ok ... I committed changes I made porting for mingw without
checking under uni
On Wed, 27 Feb 2002 09:26:34 + Richard Frith-Macdonald <[EMAIL PROTECTED]>
wrote:
>|
>| On Wednesday, February 27, 2002, at 08:46 AM, Manuel Guesdon wrote:
>|
>| > Hi,
>| >
>| > There's a bug in KVC.
>| > When constructing setValue:forKey: method name, the method in has
>| > garba
On Wednesday, February 27, 2002, at 11:19 AM, Manuel Guesdon wrote:
>> | PS. Also implemented MacOS-X compatible KVC behavior in
>> NSDictionary.m
>
> It makes troubles for me. Please see the code I've sent and WO
> specifications at
> http://developer.apple.com/techpubs/webobjects/Reference/Ja
Hi,
for some unknown reason, the configure test in GNUstep base for
NeXT_RUNTIME was set up to never use -fconstant-string-class,
see config/config. constant-string-class.m .
As you can use gcc 3.1 on Darwin / OS X, which supports this
option, I patched configure and the test to do a real te
Segmentation fault when quitting GSTest.app, likely caused by the
NSGraphicsContext dealloc patch (which doesn't necessarily imply the patch
is wrong, it might be a bug somewhere else which was discovered by the
patch).
(gdb) i stack
#0 0x40625d91 in free () from /lib/libc.so.6
#1 0x40625c13 in
Alexander Malmberg wrote:
> Hi again,
>
> In one of the recent NSApplication updates someone added a comment that
> GSCurrentContext() wasn't being dealloc:d properly. A quick search in my
> retain/release logs showed me that:
>
I think Fred put this in, but it also proded me to get rid of th
Nicola Pero wrote:
> Segmentation fault when quitting GSTest.app, likely caused by the
> NSGraphicsContext dealloc patch (which doesn't necessarily imply the patch
> is wrong, it might be a bug somewhere else which was discovered by the
> patch).
>
I'm pretty sure it's somewhere else, we only g
