Follow-up Comment #6, bug #30766 (project gnustep):
>> The later two could be ruled out by running a non GNUstep
>> Objective-C program compile don this machine.
>
> Base 1.19.3 runs fine, so I guess they can be ruled out right away.
Unfortunately not as it's perfectly possible for some code to trigger bugs in
the compiler or runtime that other code does not trigger.
>> Next you should check which of the different cases for argument
>> inspection applies in your environment.
>
>I don't have access to Debian's porter machines, but I can ask the bug
reporter to >perform whatever tests are needed.
I would guess that, in the absence of something like valgrind which will
report memory problems, what's needed is actually to run the program under gdb
and step through to find where something goes wrong.
One thing ... in the original stackdump reported I see this:
> #14 0x409e5304 in pathSeps () at NSString.m:268
but line 268 should only be executed if using mswindows style path separators
... which suggests that memory must already have been corrupted by the time
this point was reached.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?30766>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep
