id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
119	libc: logging stops in fork() child after libc data segment copying	bird	bird	"There are two problems here. First, why do we get a different file handle for the log in the child? Second, we're gambling that the log mutex and file handles match the parent.

The latter problem is solved by reallocating the child handles to match the parent ones very early in the fork process.

The former problem is answered by {{{DosDupHandle()}}} always clearing the non-inherit bit."	defect	closed	normal	libc-0.6.2	libc-backend	0.6.1	normal	fixed	log fork