[ ghc-Bugs-1222522 ] scavenge_stack: weird activation record found on stack:37548

[SourceForge.net]

Bugs item #1222522, was opened at 2005-06-17 10:43
Message generated for change (Settings changed) made by simonmar
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108032&aid=1222522&group_id=8032

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: 6.4
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Markus Laire (malaire)
Assigned to: Simon Marlow (simonmar)
Summary: scavenge_stack: weird activation record found on stack:37548

Initial Comment:
During 'make test' of pugs (http://pugscode.org/) which
is written in Haskell I got this error:

...
...
t/oo/class/nested_use..............................ok
t/oo/class/require.................................ok
        2/3 TODO bug tests
t/oo/clone.........................................ok
        3/9 TODO feature tests
t/oo/construction..................................ok
        6/7 TODO feature tests
t/oo/delegation....................................ok
        24/34 TODO feature tests
t/oo/destruction...................................ok
3/6pugs: internal error: scavenge_stack: weird
activation record found on stack: 37548
    Please report this as a bug to
glasgow-haskell-bugs at haskell.org,
    or http://www.sourceforge.net/projects/ghc/
t/oo/destruction...................................dubious
        Test returned status 254 (wstat 65024, 0xfe00)
        after all the subtests completed successfully
...
...


I have:
* GHC 6.4
* pugs r4733
* parrot r8392
* SuSe 9.1
* "uname -a" gives "Linux 2.6.5-7.155.29-default #1 Thu
Jun 2 12:07:05 UTC 2005 i686 athlon i386 GNU/Linux"


----------------------------------------------------------------------

>Comment By: Simon Marlow (simonmar)
Date: 2005-11-11 11:09

Message:
Logged In: YES 
user_id=48280

I'm reasonably sure I've fixed this, in rev. 1.276 of
ghc/rts/Schedule.c.  I wasn't able to reproduce the symptoms
using Pugs, but it is highly likely that this is the same
bug - triggered duing a GC near program termination when
there are finalizers running.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108032&aid=1222522&group_id=8032