My last experience with ruby and valgrind was kinda unpleasant. Maybe with ruby 1.9 it will be better but I don't really have the stomach for changing my entire test environment right now.
Worst still, as soon as I had packed up a tar file of the code that lead to the crash, it stopped crashing. :-( Maybe I'll get something more reproducible later. I'll post more stacktraces, etc as I get them unless the list maintainers would rather I didn't. __ Marc On Fri, 2008-11-01 at 13:47 -0500, Todd Fisher wrote: > On 1/10/08, Marc Munro <[EMAIL PROTECTED]> wrote: > > This is with libxml and libxsl built from SVN 3 days ago > > > You might try running with valgrind. > > > > If I run with gdb, my program runs normally. > > > > Any suggestions on how I can further track this down? > > > > __ > > Marc > > > > > > *** glibc detected *** ruby: corrupted double-linked list: 0x0914ed28 > > ***
signature.asc
Description: This is a digitally signed message part
_______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
