Jeremy Hinegardner wrote:
> On Wed, Jan 06, 2010 at 07:59:34AM +0900, James Edward Gray II wrote:
>> 
>> James Edward Gray II
> 
> When I have something like this, I generally will compile a debug (-g)
> version of ruby and then run the spec/test via gdb to figure it out.  Do 
> a stack
> trace in gdb and look where the free is being called and go from there.

Like Jeremy said, you could run it in gdb by re-compiling your version 
of ruby with debug symbols

http://railsquestions.blogspot.com/2009/01/compiling-ruby-with-debug-symbols-in.html

then just run it in gdb and break on malloc_error_break
valgrind might be quite useful, too [and might not require a recompile].
GL.
-r
-- 
Posted via http://www.ruby-forum.com/.