Re: weird data corruption

2006-08-24 Thread Tomasz Zielonka
On Thu, Aug 24, 2006 at 01:12:32AM +0100, Frederik Eaton wrote: Do you think that the standard GHC behavior should be for multithreaded programs to produce garbage on stderr? IIUC, even if you switch to LineBuffering on stderr, you'll still get garbage, only less often and in more subtle ways,

Re: [GHC] #875: assert fails on HEAD

2006-08-24 Thread GHC
#875: assert fails on HEAD --+- Reporter: guest| Owner: Type: bug | Status: new Priority: high | Milestone: 6.6 Component: Compiler |

Re: [GHC] #874: SEGFAULT in stg_ap_ppp_info()

2006-08-24 Thread GHC
#874: SEGFAULT in stg_ap_ppp_info() -+-- Reporter: guest | Owner: Type: bug | Status: new Priority: normal | Milestone: 6.4.3 Component: Runtime

[GHC] #876: stack overflow on 'length . filter odd $ [0 .. 999999999]'

2006-08-24 Thread GHC
#876: stack overflow on 'length . filter odd $ [0 .. 9]' +--- Reporter: [EMAIL PROTECTED] |Owner: Type: bug | Status: new Priority: normal |

[GHC] #877: Template Haskell doesn't parse data decls properly

2006-08-24 Thread GHC
#877: Template Haskell doesn't parse data decls properly +--- Reporter: [EMAIL PROTECTED] |Owner: Type: bug | Status: new

Re: [GHC] #652: Have a single Data.Typeable hash table in GHCi

2006-08-24 Thread GHC
#652: Have a single Data.Typeable hash table in GHCi ---+ Reporter: simonmar | Owner: Type: task | Status: closed Priority: high | Milestone:

Re: [GHC] #876: stack overflow on 'length . filter odd $ [0 .. 999999999]'

2006-08-24 Thread GHC
#876: stack overflow on 'length . filter odd $ [0 .. 9]' --+- Reporter: [EMAIL PROTECTED] | Owner: Type: bug | Status: new Priority: normal |

Re: weird data corruption

2006-08-24 Thread Frederik Eaton
On Thu, Aug 24, 2006 at 08:36:07AM +0200, Tomasz Zielonka wrote: On Thu, Aug 24, 2006 at 01:12:32AM +0100, Frederik Eaton wrote: Do you think that the standard GHC behavior should be for multithreaded programs to produce garbage on stderr? IIUC, even if you switch to LineBuffering on

Re: [GHC] #862: Document changes to packages

2006-08-24 Thread GHC
#862: Document changes to packages +--- Reporter: simonmar | Owner: Type: task | Status: closed Priority: high | Milestone: 6.6 Component:

Re: [GHC] #710: library reorganisation

2006-08-24 Thread GHC
#710: library reorganisation -+-- Reporter: simonmar| Owner: Type: task| Status: new Priority: normal | Milestone: Component:

Re: [GHC] #656: Provde a way to return values as Dynamic from the GHC API

2006-08-24 Thread GHC
#656: Provde a way to return values as Dynamic from the GHC API --+- Reporter: simonmar | Owner: Type: task | Status: closed Priority: normal | Milestone: 6.6

Re: weird data corruption

2006-08-24 Thread John Meacham
On Thu, Aug 24, 2006 at 02:26:42PM +0100, Frederik Eaton wrote: Because of what you said above, it's not perfect. But it's better than the default. Look, if someone is writing something to standard error, it's probably because they want to accomplish something, such as printing a message that

[GHC] #878: Loading and unloading a Haskell DLL leaks handles

2006-08-24 Thread GHC
#878: Loading and unloading a Haskell DLL leaks handles ---+ Reporter: guest |Owner: Type: bug | Status: new Priority: normal |

Re: [GHC] #875: assert fails on HEAD

2006-08-24 Thread Ian Lynagh
On Wed, Aug 23, 2006 at 11:55:06PM -, GHC wrote: [EMAIL PROTECTED] should_run]$ cat dsrun014.hs module Main where import Control.Exception ( assert ) main = assert Hello True $ print World [EMAIL PROTECTED] should_run]$ $GHC66 dsrun014.hs dsrun014.hs:5:7: Couldn't