EventLog does not play well with forkProcess
|Reported by:||adept||Owned by:||simonmar|
|Type of failure:||Incorrect result at runtime||Test Case:|
|Related Tickets:||Differential Rev(s):|
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"?