[comp.unix.ultrix] Bizarro error message

grunwald@foobar.colorado.edu (Dirk Grunwald) (10/09/90)

I got the following console message (UWS 2.2 == Ultrix 3.2) and
haven't a clue as to what it means. Does anyone know?

grow failed sp >= USRSTACK-ctob(u.u_ssize) 0x7ffff000 >= 0x7fff7000

Dirk Grunwald -- Univ. of Colorado at Boulder	(grunwald@foobar.colorado.edu)
						(grunwald@boulder.colorado.edu)

bhoughto@cmdnfs.intel.com (Blair P. Houghton) (10/09/90)

In article <1794@shodha.enet.dec.com> alan@shodha.enet.dec.com ( Alan's Home for Wayward Notes File.) writes:
>		main()
>		{
>			int	array[10] ;
>			array[999] = 0 ;
>			return 0 ;
>		}
>
>	This is a common enough error that we should document it
>	somewhere.

All this will do is give a bus-error; maybe dump core.

				--Blair

GEOMAGIC@kcgl1.eng.ohio-state.edu (Daniel OConnell) (10/10/90)

>I got the following console message (UWS 2.2 == Ultrix 3.2) and
>haven't a clue as to what it means. Does anyone know?

>grow failed sp >= USRSTACK-ctob(u.u_ssize) 0x7ffff000 >= 0x7fff7000

>Dirk Grunwald -- Univ. of Colorado at Boulder	(grunwald@foobar.colorado.edu)
>						(grunwald@boulder.colorado.edu)

Try:

limit stacksize 2048

or something bigger (in Kbytes)? That is a different message than
I remember getting related to my suggested fix though. Of course,
we are running UWS 2.1 ULTRIX 3.1C so maybe the message is
different.

Good Luck,
Dan O'Connell
geomagic@kcgl1.eng.ohio-state.edu VMS
geomagic@geo1s.mps.ohio-state.edu Ultrix
geomagic@you.must.be.joking       Wylbur

alan@shodha.enet.dec.com ( Alan's Home for Wayward Notes File.) (10/10/90)

In article <27754@boulder.Colorado.EDU>, grunwald@foobar.colorado.edu (Dirk Grunwald) writes:
> 
> I got the following console message (UWS 2.2 == Ultrix 3.2) and
> haven't a clue as to what it means. Does anyone know?
> 
> grow failed sp >= USRSTACK-ctob(u.u_ssize) 0x7ffff000 >= 0x7fff7000
>

	I know of two things that cause this.  The first is that
	the stack tried to grow normally and failed because the
	stacksize limit was too small.  As somebody else has already
	said, use the limit command built into the csh to raise the
	stack size.

	The other is that the stack tried to grow abnormally.  This
	usually caused by a bug in the program.  The simplest way to
	simulate the bug is something like;

		main()
		{
			int	array[10] ;

			array[999] = 0 ;

			return 0 ;
		}

	This is a common enough error that we should document it
	somewhere.  If you can suggest a good place try mailing
	one of the "Reader Comment" pages from the doc set.  The
	documentation people may be able to get it added.  You
	could submit an SPR to ask that the message be changed to 
	something that makes more sense, but I tried that with the 
	"todr too small" message and got a polite "We'll think about 
	it".

> Dirk Grunwald -- Univ. of Colorado at Boulder	(grunwald@foobar.colorado.edu)
> 						(grunwald@boulder.colorado.edu)


-- 
Alan Rollow				alan@nabeth.enet.dec.com