#7229: Detecting if a process was killed by a signal is impossible
----------------------------------+-----------------------------------------
Reporter: benmachine | Owner:
Type: bug | Status: new
Priority: high | Milestone: 7.6.2
Component: libraries/process | Version:
Keywords: | Os: Unknown/Multiple
Architecture: Unknown/Multiple | Failure: None/Unknown
Difficulty: Unknown | Testcase:
Blockedby: | Blocking:
Related: |
----------------------------------+-----------------------------------------
Comment(by benmachine):
I'm happy with Simon's solution (one aspect that confuses me: if you're
terminated by signal 3, you get `(3 << 8) + exit code`: what's exit code?)
but I'd be happier still, I think, with an extra constructor that's unused
on Windows. It just seems that in practice that's what people will write
in their code anyway, using a suitable `ExitCode -> Either Signal Int`
function (or, well, `Either Int Int`, to be portable against the case of
`Signal` not existing)
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/7229#comment:8>
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
