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
Hi,
I created a patch.
I'm not sure that I really understood the problem, but following patch
works well for me.
my environment is:
Linux (CentOS 5.0) kernel 2.6.18-8.1.15.el5 on VMWare Workstation
ruby 1.8.5 (2006-08-25) [i386-linux] (CentOS's latest package)
libxml 2.6.26 (CentOS's latest p
Sorry, the attached patch was wrong.
( in-message-body one is right.)
This is the right one.
2007/12/2, keisuke fukuda <[EMAIL PROTECTED]>:
> Hi,
>
> I created a patch.
> I'm not sure that I really understood the problem, but following patch
> works well for me.
>
> my environment is:
> Linux (Ce
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
