Marc, I have yet to have valgrind produce anything meaningful in debugging this environment. I have tried the suppressions, but alas, nothing. If someone can offer an effective way of using it, I am quite interested.
As for this bug, the context code is pretty simple. This is different than double-free, so it may be that the memory is being stomped on by something else. I have no insight. Please post what you can to get to the bottom of it. Dan On Jan 11, 2008, at 13:57, Marc Munro wrote: > 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 >>> *** > > _______________________________________________ > libxml-devel mailing list > libxml-devel@rubyforge.org > http://rubyforge.org/mailman/listinfo/libxml-devel _______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
