
That sounds very applicable to my issue (and unfortunately my googling missed
this, ergo my consult of haskell-cafe uberwissenmensch). When I again have
access to the aforementioned Mac this evening I'll try both disabling
optimizations and a tweaked HUnit to see if that resolves the problem and
report back then.
-KQ
Quoting Max Bolingbroke
On 6 June 2011 16:18, Jimbo Massive
wrote: Or is this bad behaviour due to HUnit doing something unsafe?
I think it may be related to this bug: http://hackage.haskell.org/trac/ghc/ticket/5129
The suggested fix is to change HUnit to define assertFailure with throwIO, but the latest source code still uses throw:
http://hackage.haskell.org/trac/ghc/ticket/5129
So this could very well be a HUnit bug.
Max
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
------------------------------------------------- This mail sent through IMP: http://horde.org/imp/