RE: internal error: weird activation record found on stack: 9
On 16 December 2004 16:12, Peter Simons wrote:
I'm getting this error in my software every now and then:
postmaster: internal error: scavenge_stack: weird activation record found on stack: 9 Please report this as a bug to glasgow-haskell-bugs@haskell.org, or http://www.sourceforge.net/projects/ghc/
The process runs just fine for several days, and then it crashes with this message out of the sudden. There is no apparent cause. I'm using a fairly recent CVS ghc to compile the program on Linux/x86.
Any idea what I can do to help tracking this bug down?
Please compile the program with -debug, then open it with gdb. Set a breakpoint on barf() and run the program: gdb> break barf gdb> run and wait for it to hit the breakpoint. Then do gdb> signal SIGABRT to get a core dump. Send the source, binary, and core dump to us. With any luck, we'll be able to track it down without running the program. Cheers, Simon
Simon Marlow writes:
Please compile the program with -debug, then open it with gdb.
Unfortunately, -debug seems to conflict with -threaded: ghc --make -threaded -debug -O -Wall [...] -o postmaster tutorial.lhs [...] Chasing modules from: tutorial.lhs [...] Compiling Main ( tutorial.lhs, .objs/Main.o ) Linking ... /usr/lib/gcc-lib/i686-pc-linux-gnu/bin/ld: cannot find -lHSrts_thr_debug collect2: ld returned 1 exit status Would compiling with -debug and without -threaded still help? Peter
I wrote:
Simon Marlow writes:
Please compile the program with -debug, then open it with gdb.
Unfortunately, -debug seems to conflict with -threaded:
ghc --make -threaded -debug -O -Wall [...] -o postmaster tutorial.lhs [...] Chasing modules from: tutorial.lhs [...] Compiling Main ( tutorial.lhs, .objs/Main.o ) Linking ... /usr/lib/gcc-lib/i686-pc-linux-gnu/bin/ld: cannot find -lHSrts_thr_debug collect2: ld returned 1 exit status
It has been a while since this problem came up, and I was wondering what to do now, because the software keeps crashing (or freezing) every few days. Any advice, anyone? Peter
Simon Marlow writes:
add "GhcRtsWays += thr_debug" to mk/build.mk in a GHC tree, and build as normal.
Great, that's gonna be no problem. Concerning your original instructions: | Please compile the program with -debug, then open it with | gdb. Set a breakpoint on barf() and run the program: | | gdb> break barf | gdb> run | | and wait for it to hit the breakpoint. Then do | | gdb> signal SIGABRT | | to get a core dump. Send the source, binary, and core | dump to us. With any luck, we'll be able to track it down | without running the program. I'll wait for the bug to occur again, before I'll do that, okay? My GHC version was several weeks old, perhaps the bug is gone (or looks different) in the most current GHC. Thanks for the help! Peter
participants (2)
-
Peter Simons -
Simon Marlow