It would be interesting to see just what is using so much stack.

	Hmm - you could unlimit the stack, run the problem generating
	program, then attach to the X server (from outside X :) with gdb
	and have a look at the backtrace... It should be obvious if we're
	having a problem with recursion :), but I don't know offhand
	how to get gdb to indicate what calls are using how much stack.

	Can anyone help on that?

		David/absolute

On Wed, 19 Jan 2000, Graham Jenkins wrote:

> >        The next stage is to work out what limit is the problem.
> >        My guess would be stack or data - could you try them one by
> >        one to identify which breaks it (assuming its only one :)
> 
> 
> Your first guess was right. None of the others fixed the problem.
>     diff ulimit.before ulimit.after
>     < stack(kbytes)        512
>     ---
>     > stack(kbytes)        262144
> 
> The offending application appears to be Netscape Communicator 4.61
> for Solaris 2.5.1 - running on Solaris 2.6 - under CDE with remote
> Xserver on the NetBSD box.  But there are probably others ..
> 
> Now what ??
> 
> G.
>