Micah Geisel wrote:
> i am having the same problem. was a solution found? did it turn out to 
> be faulty memory?

I'll let you know in a few days when I get my RAM

I ran a memtest on it and came back with no faults, but I'm getting 
other failures now in Ruby and related processes. Darwin's CrashReporter 
core dumps look a whole lot like the one I described above. I can't 
prove it but I'm suspicious of the memory, and it's cheap enough to 
replace and test it out.

I'll let you know.
-- 
Posted via http://www.ruby-forum.com/.