Ticket #3288 (closed bug: duplicate)
GC assertion failure in reactive program
| Reported by: | Baughn | Owned by: | simonmar |
|---|---|---|---|
| Priority: | high | Milestone: | 6.10.4 |
| Component: | Runtime System | Version: | 6.11 |
| Keywords: | Cc: | ||
| Operating System: | Unknown/Multiple | Architecture: | Unknown/Multiple |
| Type of failure: | Difficulty: | Unknown | |
| Test Case: | crash.hs | Blocked By: | |
| Blocking: | Related Tickets: |
Description
In the same vein as bug #3279, this time I've triggered an assertion failure in the GC by adding Debug.Trace.trace expressions.
The exact same failure occurs in both 6.10.3 and 6.11, apparently completely deterministically.
A darcs patch to add the crash to reactive, and a program to trigger it, are both attached.
Expected output:
svein@eris ~ $ ./crash
<Imp NoBound 2.0,1.0>
<Imp NoBound 2.5,2.0>
<Imp NoBound 3.2,3.0>
<Imp NoBound 3.7,4.0>
"never-never"
crash: internal error: scavenge_one: strange object 28
(GHC version 6.11.20090605 for x86_64_unknown_linux)
Please report this as a GHC bug: http://www.haskell.org/ghc/reportabug
Aborted
Attachments
Change History
Note: See
TracTickets for help on using
tickets.

