> I get the following error message:
>
> darcs: internal error: EVACUATED object entered!
> Please report this as a bug to [EMAIL PROTECTED],
> or http://www.sourceforge.net/projects/ghc/
>
> I'm not sure what is causing this. This is using ghc 6.2, the debian
> version that just moved into sarge. The situation that
> triggers this (and
> I think I've reproduced it twice, so I'm optimistic that it may be
> reproducible) is rather complex, so hints as to how to track
> this down are
> probably the best approach (as opposed to creating a simple test case,
> which seems a bit unlikely).
>
> I haven't yet tried this same code with an older (or newer)
> ghc, so I don't
> know if this is a new problem. The test case as it
> currently exists takes
> sever hours of thrashing to disk before crashing. I may be
> able to improve
> the time to crash dramatically, but am on vacation now and am
> not sure when
> I'll have time to work more on this.
The best plan of attack is to try to make the bug reproducible, and with
as little runtime before the crash as possible. Try to eliminate any
non-deterministic effects in your program (eg. the use of random
temporary filenames is one source of non-determinism that is easy to
overlook).
It's hard to say what the problem is at this stage, but it looks to be
GC-related. Get to a reproducible point, then ship us the code and I'll
look into it.
Cheers,
Simon
_______________________________________________
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
