apologize for late response,
I applied Keisuke's patch and it looks like it works, script no longer
causes Segmentation fault,
below there is some data on seg faults I experienced and on my
environment:
my system:
[EMAIL PROTECTED]:~$ uname -a
Linux pkopyt 2.6.15-23-686 #1 SMP PREEMPT Tue May 23
to_s <=> other.to_s
end
+
+ def clone
+copy(false)
+ end
end
class XML::Attr
Index: tests/tc_xml_node_copy.rb
===
--- tests/tc_xml_node_copy.rb (revision 0)
+++ tests/tc_xml_node_copy.rb (revision 0)
@@ -0,0 +1,40 @@
+require "lib
> --- ext/xml/libxml.rb (revision 220)
> +++ ext/xml/libxml.rb (working copy)
> @@ -72,6 +72,14 @@
>def <=>(other)
> to_s <=> other.to_s
>end
> +
> + def clone
> +copy(false)
> + end
> end
>
> class XML::Attr
> Index: tests/tc_xml_node_copy.rb
>
I have not been able to reproduce this SEGV on two different
processor architectures. Any additional effort or debugging would be
necessary.
Yes, _private is for application use.
Dan
___
libxml-devel mailing list
libxml-devel@rubyforge.org
http://ru
Sorry, I made some misunderstanding.
The libxml source that I looked at was somewhat old,
and the latest source says that _priavte is for application data.
So, using _private to store VALUE is valid way.
But, the set-to-null problem is still there... :-(
07/11/29 に keisuke fukuda<[EMAIL PROTECTE
Hi,
I've been trying this problem these days.
For now I've not yet reached to an answer, but this may be a hint :
gdb told me that the problem is about memory allocation,
especially a double-freeing problem.
Changing optyk's script like this :
div2.each do |child|
#c = child.clone
c = child
hello,
I get segmentation fault when add the cloned/copied node to other
node,
script to problem reproduction below,
segv appears when use clone and copy methods,
what's interesting, with clone segv is thrown in div1.child_add(c)
line (see script)
but when use copy I get it in printf root stateme
