If you have an Xsun.core in the / directory, you can (as root):

	gdb /usr/X11R6/bin/Xsun /Xsun.core 

	Which should include the line 	
	'Program terminated with signal 11, Segmentation fault.'

	If it was compiled with -g then 'bt' would show the function and
	line at which it died. If I can cobble together the spare space I
	might just compile a new server with -g :)

		David/absolute

	 -=-  "Just adding to the wrinkles on his deathly frown"  -=-

On Wed, 6 May 1998, Brad Salai wrote:

> I've seen this for a while. I originally thought it was a Netscape problem, and it may be, but it has existed for a while, 4.0.1 to 4.0.5 at least.
> 
> I'd pass along the cause of death, but I'm a rookie, how do I tell if it is SEGV?
> 
> Brad
> David Brownlee said
> > 	I thought about that - but its dying with a SEGV... 
> > 
> > 		David/absolute
> > 
> > 	 -=-  "Just adding to the wrinkles on his deathly frown"  -=-
> > 
> > On Sun, 3 May 1998, Jukka Marin wrote:
> > 
> > > On Sat, May 02, 1998 at 09:41:25PM -0700, David Brownlee wrote:
> > > > 	I've also seen something similar when I use the SunOS Netscape
> > > > 	under 1.3.1 - if I browse enough Xsun will die. I keep meaning
> > > > 	to compile Xsun -g to see why....
> > > 
> > > Maybe it hits the per-process data limit?
> > > 
> > >   -jm
> > > 
> > 
> > 
>