🚀 go-pugleaf

I can start Xsun on a Sun 4/110 with an initial client of xterm.  I
can start additional xterms from within the initial xterm and that
goes well. However, if I start any other client (well, I have only
tried xeyes and twm) the server core dumps with a sigsegv. The core
dump file was big (8 MB) so on a hunch I set my stack size limit to
the maximum.  It then produced a 400MB core file. (Fortunatly this
seems to be mostly unallocated blocks so it doesn't actually take up
that much space).


It seems like the server is writing past the top(or bottom) of it's
stack, but why?  There is also something in the back of my mind which
says that xterm works because it is suid and that I have some
permissions somewhere set wrongly but I can't think what it might be.

The same clients work with Xsun on 3/60 machines.

Has anyone else seen this? Or better still, got a fix?
-- 
 Ian Dall           life (n). A sexually transmitted disease which afflicts
                              some people more severely than others.
idall@augean.oz