Re: Signal inconsistency between GHC and GHCi

Am Sonntag, 1. Januar 2006 19:40 schrieb Bulat Ziganshin: > Sunday, January 01, 2006, 2:27:01 PM, you wrote: > >> >> [ usleep/nanosleep trouble deleted... ] > >> > >> may be you comile with -threaded? ghci don't use this option, afaik > > SP> The SIGALRM happen with purely interpreted code and even

Re[2]: Signal inconsistency between GHC and GHCi

Hello Sven, Sunday, January 01, 2006, 2:27:01 PM, you wrote: >> >> [ usleep/nanosleep trouble deleted... ] >> >> may be you comile with -threaded? ghci don't use this option, afaik SP> The SIGALRM happen with purely interpreted code and even without loading any SP> code at all into GHCi... :-(

Re: [GHC] #643: div and mod return wrong result

#643: div and mod return wrong result +--- Reporter: anonymous | Owner: Type: bug| Status: closed Priority: normal | Milestone: Component: GHCi |

[GHC] #643: div and mod return wrong result

#643: div and mod return wrong result --+- Reporter: anonymous |Owner: Type: bug| Status: new Priority: normal |Milestone: Component: GHCi |

Re: Signal inconsistency between GHC and GHCi

Am Mittwoch, 28. Dezember 2005 14:05 schrieb Bulat Ziganshin: > Wednesday, December 28, 2005, 3:28:07 PM, you wrote: > >> [ usleep/nanosleep trouble deleted... ] > > may be you comile with -threaded? ghci don't use this option, afaik The SIGALRM happen with purely interpreted code and even without