Charlie Savage wrote:
Which ultimately originates in line 1049 in gc.c ( function gc_mark_children ) in ruby-1.8.7-p72
Any ideas?

If you can easily duplicate the issue (sounds like it), then what I would do is run the program under a debugger like gdb or VC++. Put a breakpoint in the relevant mark functions defined in the libxml library. Then step through them and see if you can see what's going on.

Or put a breakpoint in the ruby source code that is raising the exception, and inspect the backtrace. On Windows you won't have any luck with that since the Ruby executable doesn't have symbol information, but maybe your platform is different.
I will give it a try, but I haven't used gdb in ages.

--
Dmitri Priimak
_______________________________________________
libxml-devel mailing list
libxml-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/libxml-devel

Reply via email to