#7229: Detecting if a process was killed by a signal is impossible --------------------------------------+------------------------------------ Reporter: benmachine | Owner: Type: bug | Status: new Priority: high | Milestone: 7.8.1 Component: libraries/process | Version: Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Unknown/Multiple Type of failure: None/Unknown | Difficulty: Unknown Test Case: | Blocked By: Blocking: | Related Tickets: --------------------------------------+------------------------------------ Comment (by hvr): Replying to [comment:30 andersk]:

* The documentation clearly calls out that our encoding is byte-swapped from the standard one for historical reasons.

Yeah, I've planned to enhance the documentation related to `exitWith`, and for the two functions in `process` to reflect the new non-windows encoding.

* We might as well include the core dump bit as bit 15 for completeness. It’s useful for printing messages like `Segmentation fault (core dumped)`, and I don’t see a downside as long as we do it now. glibc, Perl, and Python all provide it as bit 7.

...I'm not against that, but what should `safeExit` do in that case? with the current patch this would cause `other /= 0` and thus terminate normally with exit code 255. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/7229#comment:31 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler