Date: Tue, 15 Apr 1997 23:01:18 -0500 (EST) From: "John S. Dyson" <toor@dyson.iquest.net> To: current@freebsd.org Subject: You will need to recompile your libc and apps!!! Message-ID: <199704160401.XAA03609@dyson.iquest.net>
next in thread | raw e-mail | index | archive | help
There is a serious bug in popen that has gone undetected until now. I have just committed a fix that makes the shared address space vfork problem go away (which was due to the popen boo-boo.) I will not be committing the fix to vfork until people have a chance to recompile their libc and re-link their apps with the corrected library. If you try to use the new (semantically correct) vfork with the broken library, you will experience some unexpected hangs in apps that use popen once in a while. The hangs are algorithmically reproduceable. It is unlikely that you will have to do anything to applications that are dynamically linked (other than install the new shared libc.) Statically linked apps are problematical. Vfork will be fixed soon, so at that time (perhaps a few days), you'll likely start noticing problems with things like the "man" and "sgmlfmt" commands (like you might have been seeing before I backed out the semantic correction for vfork.) If this grossly inconviences anyone, we can probably support a temporary kernel option for a few weeks until you have a chance to upgrade. Any problems with fixing vfork on Friday? Or will we need to support the temporary measure for backwards compatibility with the broken library routine? John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704160401.XAA03609>