On Thu, Jul 09, 2009 at 10:01:37AM -0700, Don Stewart wrote:
> john:
> > I noticed that programs compiled with GHC 6.10 seem to be eating signals
> > and exiting with an error code of 255, rather than the proper exit code
> > for the signal that killed the process.
> >
> > I can understand that th
john:
> I noticed that programs compiled with GHC 6.10 seem to be eating signals
> and exiting with an error code of 255, rather than the proper exit code
> for the signal that killed the process.
>
> I can understand that the GHC runtime may need to perform some cleanup
> on a SIGINT or other sig
I noticed that programs compiled with GHC 6.10 seem to be eating signals
and exiting with an error code of 255, rather than the proper exit code
for the signal that killed the process.
I can understand that the GHC runtime may need to perform some cleanup
on a SIGINT or other signal, but instead o
