On 15/01/2012 00:07, Gabor Greif wrote:
Hello hackers,

my "hello world" program compiles and links, but when running on the
embedded PowerPC board it crashes like this:

(gdb) run
Starting program: /root/test
test: internal error: stg_ap_p_ret
     (GHC version 7.5.20120111 for powerpc_unknown_linux)
     Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug

Program received signal SIGABRT, Aborted.
0x0fdc0a4c in raise () from /lib/tls/libc.so.6
(gdb) bt
#0  0x0fdc0a4c in raise () from /lib/tls/libc.so.6
#1  0x0fdc2488 in abort () from /lib/tls/libc.so.6
#2  0x1029b300 in rtsFatalInternalErrorFn ()
#3  0x1029b024 in barf ()
#4  0x102b3f9c in stg_ap_p_info ()
#5  0x1029d0ac in scheduleWaitThread ()
#6  0x102c69a8 in rts_evalLazyIO ()
#7  0x1029ae80 in real_main ()
#8  0x1029afc8 in hs_main ()
#9  0x10002168 in main ()
(gdb) c
Continuing.

Program terminated with signal SIGABRT, Aborted.
The program no longer exists.

This back trace tells us almost nothing, I'm afraid - many different kinds of corruption end up as crashes in stg_ap_p_info or some other bit of the RTS.

I suggest following the instructions in

  http://hackage.haskell.org/trac/ghc/wiki/Debugging/CompiledCode

and see how far you get.  Come back if you get stuck.

Cheers,
        Simon






'git grep' does not turn up any hits for 'stg_ap_p_info', and
'scheduleWaitThread' looks pretty much innocent. Where is the best
place to get into debugging this?

I gather stg_ap_p_info is a (global data) StgInfoTable, but then again
it appears in the backtrace, (tables beside code?). Why would it barf
at all?

I am thinking that some host configury may still be leaking into the
target, so I might be fighting a deceived RTS ('revenge tastes best
when served cold'). But the host and target should be pretty
comparable linux OSs.

I am thankful for any hints.

Cheers,

     Gabor

_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc


_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc

Reply via email to