freebsd-dev/tools/regression/environ/Makefile.envctl

#
# $FreeBSD$
#
SRCS=	envctl.c
PROG=	envctl

CFLAGS+=-Wall -I../../../include

CLEANFILES=	${PROG}.core

NO_MAN=	yes

.include <bsd.prog.mk>

test: ${PROG}
	@env -i sh envtest.t
Significantly reduce the memory leak as noted in BUGS section for setenv(3) by tracking the size of the memory allocated instead of using strlen() on the current value. Convert all calls to POSIX from historic BSD API: - unsetenv returns an int. - putenv takes a char * instead of const char *. - putenv no longer makes a copy of the input string. - errno is set appropriately for POSIX. Exceptions involve bad environ variable and internal initialization code. These both set errno to EFAULT. Several patches to base utilities to handle the POSIX changes from Andrey Chernov's previous commit. A few I re-wrote to use setenv() instead of putenv(). New regression module for tools/regression/environ to test these functions. It also can be used to test the performance. Bump __FreeBSD_version to 700050 due to API change. PR: kern/99826 Approved by: wes Approved by: re (kensmith) 2007-07-04 00:00:41 +00:00			`#`
			`# $FreeBSD$`
			`#`
			`SRCS= envctl.c`
			`PROG= envctl`

			`CFLAGS+=-Wall -I../../../include`

			`CLEANFILES= ${PROG}.core`

			`NO_MAN= yes`

			`.include <bsd.prog.mk>`

			`test: ${PROG}`
Do not gratuitously fail env(3) operations due to corrupt ('='-less) *environ entries. This puts non-getenv(3) operations in line with getenv(3) in that bad environ entries do not cause all operations to fail. There is still some inconsistency in that getenv(3) in the absence of any environment-modifying operation does not emit corrupt environ entry warnings. I also fixed another inconsistency in getenv(3) where updating the global environ pointer would not be reflected in the return values. It would have taken an intermediary setenv(3)/putenv(3)/unsetenv(3) in order to see the change. 2009-12-01 05:04:31 +00:00			`@env -i sh envtest.t`