Excerpts from Tyson Whitehead's message of Sun Feb 20 07:14:56 -0500 2011:
> I believe a back trace on the actual call stack is generally considered not
> that useful in a lazy language as it corresponds to the evaluation sequence,
> That is, it is demand centric while written code is production
Good work!
The HP team is ready to go!
-- Don
igloo:
>
> We are pleased to announce the second release candidate for GHC 7.0.2:
>
> http://www.haskell.org/ghc/dist/7.0.2-rc2/
>
> This includes the source tarball, the Windows installer, and bindists
> for 32bit and 64bit Intel OS X, amd64/
We are pleased to announce the second release candidate for GHC 7.0.2:
http://www.haskell.org/ghc/dist/7.0.2-rc2/
This includes the source tarball, the Windows installer, and bindists
for 32bit and 64bit Intel OS X, amd64/Linux, i386/Linux, amd64/FreeBSD
and i386/FreeBSD.
Please test as muc
On February 19, 2011 12:11:13 Edward Z. Yang wrote:
> I was thinking it might be useful if we had a per-thread circular buffer in
> memory for which we pushed a pointer to the info table we had just entered.
> In the event of a crash, you could dump the contents of the buffer to see
> what code ha
