[Haskell-cafe] New runtime crash, not sure what to make of it
Simon Marlow
simonmar at microsoft.com
Wed Dec 7 07:09:21 EST 2005
On 07 December 2005 00:51, Joel Reymont wrote:
> Program compiled with -threaded on Mac OSX. Crash happens when
> waiting in select, I think.
>
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_PROTECTION_FAILURE at address: 0x00000000
> [Switching to process 832 thread 0x2303]
> 0x0011ce20 in stg_enter_info ()
> (gdb) where
> #0 0x0011ce20 in stg_enter_info ()
> #1 0x00170e7c in StgRunIsImplementedInAssembler ()
> #2 0x001247a4 in schedule ()
> #3 0x00124468 in taskStart ()
> #4 0x0017f800 in startProcWrapper ()
> #5 0x9002b200 in _pthread_body ()
>
> Haskell stack trace:
>
> (gdb) p16 $r22
> 0x130a87c: 0x130a898
> 0x130a878: 0x13162c <selw_info>
> 0x130a874: 0x2a
> 0x130a870: 0x1305000
> 0x130a86c: 0x1b6aec <sdG0_info>
> 0x130a868: 0x130a884
> 0x130a864: 0x20e174 <GHCziIOBase_bindIO_closure>
> 0x130a860: 0x20e17c <GHCziIOBase_returnIO_closure>
> 0x130a85c: 0x1315b0 <selK_info>
> 0x130a858: 0x130a878
> 0x130a854: 0x130a86c
> 0x130a850: 0x20e174 <GHCziIOBase_bindIO_closure>
> 0x130a84c: 0x10002 <s7uY_dflt+38>
> 0x130a848: 0x1174c0 <stg_PAP_info>
> 0x130a844: 0x170114 <stg_stop_thread_info>
> 0x130a840: 0x170208 <stg_noforceIO_info>
> 0x130a83c: 0x118bd0 <stg_ap_v_info>
Strange. This might be related to async exceptions, are you doing any
killThreads or throwTos?
Can you also generate a scheduler trace (+RTS -Ds) up to the crash
point? And it might help to dump out the state of the current thread:
gdb> print MainCapability.r.rCurrentTSO
should do it.
Cheers,
Simon
More information about the Glasgow-haskell-bugs
mailing list