>Number:         3045
>Category:       bin
>Synopsis:       Foolishly limiting your stack should be less fatal
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Dec 19 01:20:00 1996
>Last-Modified:
>Originator:     Jason R Thorpe
>Organization:
Numerical Aerodynamic Simulation Project - NASA Ames
>Release:        December 18, 1996, NetBSD 1.2B
>Environment:
	
System: NetBSD lestat 1.2B NetBSD 1.2B (Lestat) #60: Mon Dec 2 13:58:14 PST 1996 thorpej@lestat:/tmp_mnt/antie/work/netbsd/src/sys/arch/sparc/compile/Lestat sparc


>Description:
	In `sh', setting your stack limit to 0 causes the shell to
	execute an illegal instruction.

>How-To-Repeat:
	$ ulimit -s
	262144
	$ ulimit -s 0
	Illegal instruction (core dumped)
	lestat (thorpej) /sys/arch/i386/include 1244%

>Fix:
	I didn't investigate the bug, so I don't have a fix.  I sort
	of stumbled on the problem accidentally, found it at least
	a little amusing, and then decided to file a bug report on
	it.  While setting such a limit is arguably quite stupid,
	the shell probably ought to not allow such foolishness.
>Audit-Trail:
>Unformatted: