Re: [GHC] #7229: Detecting if a process was killed by a signal is impossible

#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:32 andersk]:
`safeExit` should just ignore the coredump flag. (The process can’t control whether the `SIG_DFL` action for that signal results in a core dump—the list of such signals is defined by the kernel, e.g. `SIG_KERNEL_COREDUMP_MASK` in Linux.)
ok, so - `safeExit 0x8300` would be handled like `safeExit 0x0300` but what should happen for the corner-cases - `safeExit 0x8000`, or - `safeExit 0x8001`, or - `safeExit 0x18000` ? -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/7229#comment:33 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler
participants (1)
-
GHC