> I think this is a bug in ghc 5.03 (whatever is in the CVS).
> Please excuse me if I'm wrong.
>
> file: ghc/rts/Stable.c
>
> symptom: seg faults sometimes (tricky to reproduce, but occurs when
> you have more than one live stable pointer to the same value,
> and a bunch of other live stable pointers around at the same
> time). The order that you free and allocate makes a
> difference
> as to whether you see the bug or not.
>
> reason: corruption of the stable pointer table due to the
> premature freeing of an entry in the stable pointer
> table -- the pointer stable_ptr_free becomes corrupt
> and points to something outside the table.
>
> possible fix: Do not call freeStableName on an entry in the
> stable pointer table if its reference count is
> not zero.
Good point, I've committed your patch. If you have some code that
triggers the bug, I'd be interested so we can put it in the regression
suite.
Thanks,
Simon
_______________________________________________
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
