Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#119 closed defect (fixed)

libc: logging stops in fork() child after libc data segment copying

Reported by: bird Owned by: bird
Priority: normal Milestone: libc-0.6.2
Component: libc-backend Version: 0.6.1
Severity: normal Keywords: log fork


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.

Change History (2)

comment:1 Changed 13 years ago by bird

  • Resolution set to fixed
  • Status changed from new to closed

(In [2796]) Fixed log problem in fork() child. Fixes #119.

comment:2 Changed 13 years ago by bird

(In [2797]) Fixed log problem in fork() child. Fixes #119. (from 0.6)

Note: See TracTickets for help on using tickets.