* Scott Burton (scottburton11 / gmail.com) wrote:

> "Cannot access memory" looks suspiciously like bad RAM....

No, that just means the value on the stack isn't a valid memory address
for the process; that, plus the NULLs and the duplicated values in the
backtrace suggest, as gdb says, corrupt stack.  The behavior does look
like bad RAM, though.

> Unfortunately I don't have memtest on this box.

http://matt.ucc.asn.au/memtest/ any use?

-- 
Thomas 'Freaky' Hurst
    http://hur.st/