Date: Sun, 25 Oct 2015 02:47:54 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 189805] setenv with value == NULL coredumps on FreeBSD Message-ID: <bug-189805-8-NxzIgml1m0@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-189805-8@https.bugs.freebsd.org/bugzilla/> References: <bug-189805-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189805 --- Comment #3 from Garrett Cooper,425-314-3911 <ngie@FreeBSD.org> --- (In reply to Jilles Tjoelker from comment #2) An assert and adding behavior so it would return as described in comment # 0 would be better than a segfault. We have a ton of applications at $work that are multithreaded, and it peeves me off when they segfault and we have to go track down why. Dereferencing NULL is inconsistent with other OSes and makes us look silly -- especially when it's not documented. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-189805-8-NxzIgml1m0>