Charlie,
If they are the ones I am thinking of, they are going away entirely
(no longer needed). If they were in ruby_xml_{node,document,attr}.c,
there are gone now. They will be in modules I have not touched yet,
but they will go too.
There is no code carried forward for ruby_xml_*_new or
ruby_xml_*_free, the memory management is completely different.
Everything is GC friendly and one xmlNode will only have one ruby
VALUE object associated with it at a time.
Dan
On Aug 29, 2007, at 14:31, Charlie Savage wrote:
> Dan,
>
> If you have a second, could you fix the free/xfee issue (or I can
> do it once you are done, I just don't want to interfere with what
> you are doing).
>
> The problem is that various structures in libxml are allocated with
> the macro ALLOC, which means the ruby executable is creating the
> memory. But the structures are then deallocated using free, which
> means the dll is trying to delete them. On windows this doesn't
> work since each dll likely has its own stack (depending on the
> runtime library it is using).
>
> The solution is simple - use xfree (which is what you are supposed
> to use anyway for memory created via ALLOCA) and not free. There
> are about 10 to 15 instances of this in the current code base.
>
> Thanks,
>
> Charlie
>
>
> _______________________________________________
> 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
