From owner-freebsd-bugs  Mon Mar 10 14:30:08 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA03273
          for bugs-outgoing; Mon, 10 Mar 1997 14:30:08 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA03245;
          Mon, 10 Mar 1997 14:30:02 -0800 (PST)
Date: Mon, 10 Mar 1997 14:30:02 -0800 (PST)
Message-Id: <199703102230.OAA03245@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: Eric Fang <chern@tiger.towson.edu>
Subject: Re: bin/2925: non-priviledged user can crash FreeBSD!! 
Reply-To: Eric Fang <chern@tiger.towson.edu>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR bin/2925; it has been noted by GNATS.

From: Eric Fang <chern@tiger.towson.edu>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: bin/2925: non-priviledged user can crash FreeBSD!! 
Date: Mon, 10 Mar 1997 11:58:42 -0500 (EST)

 On Sun, 9 Mar 1997, Jordan K. Hubbard wrote:
 
 > > background running.  The system simply crashed and stopped.  I waited for 
 > 
 > Are you *positive* that the system crashed, e.g. you tried to access
 > it from another network node and it did not respond?  If you're
 
 No, I tested on the local machine *without* running X.  I simply hit
 'alt-F2' and logon as root and run top to see what's going on while the
 'alt-F1' console running that bad program with infinite creating
 pointers.  You can reproduce it yourself (2.1.5, for other version I have
 no idea).  Again, no X involved, no other funky processes running, and
 it's a fresh startup.
 
 > running X and you run out of swap space, many times the system will
 > shoot down the X server in its desparate attempt to find more memory
 > resources.  Unfortunately, when the X server is shot unexpectedly like
 > this it leaves the console in a bad state and it looks to the
 > uninitiated like a system crash.  You must verify that it really *was*
 > a system crash by seeing if the system is still up after you reproduce
 > the failure.  Also, don't run an X server while testing these sorts of
 > things - it only complicates the situation.  Thanks.
 > 
 > 					Jordan
 >