On Nov 18, 2005, at 2:47 PM, Simon Marlow wrote:
That doesn't tell us much unfortunately. Can you send a disassembly of the block in which the crash happened?
Is it always the same block, BTW? Does changing the heap size (+RTS -H<size>) have any effect?
I don't think changing the heap size has any effect. I tried a run
with -H512m and the only difference was that it crashed at 0x00000005
with the same kernel protection failure. The address for s34n_info is
the same, everything else the same, including stack trace and
addresses and offsets in it.
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000000
0x0024ef88 in s34n_info ()
(gdb) where
#0 0x0024ef88 in s34n_info ()
#1 0x00211eb4 in StgRunIsImplementedInAssembler () at StgCRun.c:576
#2 0x0020f048 in schedule (mainThread=0x1100360,
initialCapability=0x2fd508) at Schedule.c:932
#3 0x0020fff0 in waitThread_ (m=0x1100360, initialCapability=0x0) at
Schedule.c:2156
#4 0x0020fed4 in scheduleWaitThread (tso=0x13c0000, ret=0x0,
initialCapability=0x0) at Schedule.c:2050
#5 0x0020cd70 in rts_evalLazyIO (p=0x29216c, ret=0x0) at RtsAPI.c:459
#6 0x001d80fc in main (argc=2212180, argv=0x2fd508) at Main.c:104
(gdb) disas 0x0024ef88
Dump of assembler code for function s34n_info:
0x0024ef70