Follow-up Comment #7, bug #21415 (project gnustep):
I'm losing track here ...
The initial report was for sparc32/openbsd, but the problem is not a general
sparc32 issue as sparc32/solaris works fine.
Sebastian has a crash on sparc64/openbsd. His stacktrace looks like an
ffcall related issue and is totally different from the original one.
Greg's problem does not specify whether it's 32 or 64 bit. The stack looks
like the original problem, but Greg says this is on startup, and Sebastian's
is clearly after startup when a client is sending a message to the server.
So it looks like there might be two separate problems, one on sparc32/openbsd
and the other on sparc64/openbsd.
If someone can give me access to an account on the relevant machines I can
look at things under debug today (tomorrow I set off for FOSDEM and won't be
back until Tuesday). Alternatively/additionally it would be good to get some
clarity by, for each os/architecture, checking the following.
1. is the crash actually on startup or when a client connects?
2. does the crash occur both when running autolaunched and when started
manually and when started manually without forking?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?21415>
_______________________________________________
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
