From: Godmar Back (gback@cs.utah.edu)
Date: Mon Feb 08 1999 - 13:37:17 EST
>
> I've got a very slow host running SunOS 4.1.3. The good news is that
> dlopen is now working on it. The bad news is that nothing else is :-(
>
> Something is randomly breaking the state saved by setjmp() at thread
> initialization; it usually ends up core dumping, but the core is
> unusable because the stack is completely trashed.
>
> Within gdb, the problem occurs quite frequently, always in thread
> creation, in the second return from setjmp(). My guess was that the
> problem was related with the signal handler being invoked while
> setjmp() or longjmp() were running, which might cause the register
> window to fill up, so that registers would have to be saved in the
> stack frame. However, even when I blocked signals before setjmp() and
> unblocked them after it and in the beginning of start_this...(), the
> problems remained... Any suggestions? Should we increase the size of
> the initially copied stack frame?
>
Check your SP_OFFSET first.
I'll check in my sp_offset.c program.
- Godmar
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:58:01 EDT