Akinori MUSHA 5c08c7d35d Work around a buffer overflow problem on argv that has been exposed ... after making test(1) a sh(1) builtin; sh(1) coredumps when you run something like this: sh -c 'test ! `true 1`' The cause is that the test(1) code totally depends on the presence of two extra cells at the end of argv that are filled with NULL's. The reason why the bug hasn't been exposed would be because the C startup code kindly prepares argv with some extra zeroed cells for a program. I know this is not the best fix, but since there are argv++'s without boundary checks everywhere, I'd rather patch it up like this (preparing a copy of argv with extra NULL's) for the moment. MFC after: 3 days		2002-02-03 10:01:49 +00:00
..
Makefile	Default to WARNS=2. Binary builds that cannot handle this must explicitly	2001-12-04 01:57:47 +00:00
test.1	Make test(1) a builtin command of our sh(1) for efficiency. The	2001-11-17 19:10:11 +00:00
test.c	Work around a buffer overflow problem on argv that has been exposed	2002-02-03 10:01:49 +00:00
TEST.csh	$Id$ -> $FreeBSD$	1999-08-27 23:15:48 +00:00
TEST.README	$Id$ -> $FreeBSD$	1999-08-27 23:15:48 +00:00
TEST.sh	Remove test for block device.	2000-05-07 08:56:21 +00:00