# export x=''
# awk
SIGSEGV
This prompted a bugfix in revision 9054:
http://busybox.net/cgi-bin/viewcvs.cgi?view=rev&rev=9054 [^]
However, the core problem lies with ash. It maintains the environment as an array of strings of the form 'name=value', but this format is not respected by setvar() as invoked by the export builtin. To demonstrate, note the different results for x and y:
~ # env
USER=root
HOME=/
LOGNAME=root
TERM=vt102
PATH=/usr/sbin:/bin:/usr/bin:/sbin
SHELL=/bin/sh
PWD=/
# y=''
# export y
# env
USER=root
HOME=/
LOGNAME=root
TERM=vt102
PATH=/usr/sbin:/bin:/usr/bin:/sbin
SHELL=/bin/sh
y=
PWD=/
# export x=''
# env
USER=root
HOME=/
x
LOGNAME=root
TERM=vt102
PATH=/usr/sbin:/bin:/usr/bin:/sbin
SHELL=/bin/sh
y=
PWD=/
All entries in the environment should conform to the 'name=value' convention, as any consumers of environment variables set by ash may be susceptible to segfaults similarly to awk.
ash-export-empty-envvars.patch [^] (407 bytes) 05-18-05 21:29 
