summaryrefslogtreecommitdiffstats
path: root/lib/libthr/thread/thr_init.c
diff options
context:
space:
mode:
authorkensmith <kensmith@FreeBSD.org>2007-10-30 05:03:37 +0000
committerkensmith <kensmith@FreeBSD.org>2007-10-30 05:03:37 +0000
commit9a82deac9e7798e8b266554e32ecacef71ffdee1 (patch)
tree7da16b4aad42f7dd98080266b753a41aee74e523 /lib/libthr/thread/thr_init.c
parent9a9592dceb6f0e4272fe29a22e426edd9092ae74 (diff)
downloadFreeBSD-src-9a82deac9e7798e8b266554e32ecacef71ffdee1.zip
FreeBSD-src-9a82deac9e7798e8b266554e32ecacef71ffdee1.tar.gz
Selecting amd and a few other things in the Networking config section
caused a segfault. It turns out that in pre-7.0 systems if you do getenv("amd_enable=YES") it will return the setting of the environment variable "amd_enable" but now it returns NULL. I think I found the places where sysinstall was potentially relying on that old behavior. Fix is to make a copy of the string to be used for the getenv(3) call, look for a '=' character in it, and replace it with '\0' if one is found. Stuck to sysinstall's typical coding standards despite urges to do otherwise. PR: 117642 MFC after: 2 days
Diffstat (limited to 'lib/libthr/thread/thr_init.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud