#4512: EventLog does not play well with forkProcess
---------------------------------+------------------------------------------
Reporter: adept | Owner:
Type: bug | Status: new
Priority: normal | Component: Runtime System
Version: 7.0.1 | Keywords:
Testcase: | Blockedby:
Os: Unknown/Multiple | Blocking:
Architecture: Unknown/Multiple | Failure: Incorrect result at runtime
---------------------------------+------------------------------------------
I am trying to see an eventlog of process that daemonizes itself via
forkProcess.
Unfortunately, as parent process dies, he writes out his eventlog (or at
least a header part, I haven't checked exactly), and eventlog of the child
process is then appended to the same file.
As a result, neither ghc-events nor threadscope is able to read the
eventlog file.
I've modified the program so that it would not fork, and generated "good"
eventlog. I'm attaching it and "bad" eventlog as well so you can see the
difference by yourself.
Perhaps "+RTS -ls" could write output to filename that includes the PID of
the process, like "program.$PID.eventlog"?
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/4512>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
