stg_PAP_info crash

[Joel Reymont]

I don't know how it happened but I somehow managed to link a library  
compiled with STM against some chunks of an executable that used  
regular MVar's and Chan's for the same arguments.

Rebuilding the two modules that comprise the executable and re- 
linking solved the issue.

On Dec 17, 2005, at 7:32 PM, Joel Reymont wrote:

> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_INVALID_ADDRESS at address: 0x3c400050
> 0x3c400050 in ?? ()
> (gdb) where
> #0  0x3c400050 in ?? ()
> Cannot access memory at address 0x3c400050
> Cannot access memory at address 0x3c400050
> Cannot access memory at address 0x3c400050
> #1  0x00298b9c in stg_PAP_info ()
> Cannot access memory at address 0x3c400050
> #2  0x002d92cc in schedule ()
> #3  0x002d9e94 in waitThread_ ()
> #4  0x002d9dac in scheduleWaitThread ()
> #5  0x002d0c50 in rts_evalLazyIO ()
> #6  0x000521b8 in main ()

--
http://wagerlabs.com/