I tested it on GHC 6.12.1, which wasn't affected by the recent "ackermann" bug, but still it leaks memory.
Petr Pudlak 2013/4/22 Clark Gaebel <cgae...@uwaterloo.ca> > I don't have a copy of GHC HEAD handy, and don't have the time to set up > the ecosystem myself to test this one bug. > > Would someone else with a copy lying around mind testing it out for me? > > Thanks, > - Clark > > On Monday, April 22, 2013, Joachim Breitner wrote: > >> Hi, >> >> Am Montag, den 22.04.2013, 16:44 -0400 schrieb Clark Gaebel: >> > More interestingly, the problem goes away if I enable profiling. >> > That's kind of worrisome. >> >> this part sounds similar than the recently discussed problem with the >> ackermann function (http://hackage.haskell.org/trac/ghc/ticket/7850) – >> maybe your code is only allocating stacks and nothing else? In that case >> you can try with GHC HEAD and see if the problem is fixed. >> >> Greetings, >> Joachim >> >> >> -- >> Joachim "nomeata" Breitner >> Debian Developer >> nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C >> JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata >> >> > _______________________________________________ > Haskell-Cafe mailing list > Haskell-Cafe@haskell.org > http://www.haskell.org/mailman/listinfo/haskell-cafe > >
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
