View Issue Details

IDProjectCategoryView StatusLast Update
0000710LDMud 3.3Runtimepublic2010-03-14 17:12
ReporterWildcat Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionunable to reproduce 
Summary0000710: xml2 xml_generate non-functional in 3.3 trunk
Description(Also 3.3.719 isn't a valid product version in the mantis which is probably why i reported my last bug as 718 without noticing)

I'm using the 3.3 trunk as of this morning and compiled my driver with --enable-use-xml=xml2
using internal tools I verified it's enabled:
eval return __XML_DOM__
Returned: 1
eval return xml_parse("<abc/>")
Returned: ({ /* 0000001, size: 3 */
  "abc",
  0,
  0
})
return xml_generate(xml_parse("<abc/>") )
Returned: ""

Anything I try with generating a XML file even following the ones in the xml_generate efun simply returns an empty string instead. I've just installed iksemel and will verify that shortly.
TagsNo tags attached.

Activities

zesstra

2009-12-23 04:05

administrator   ~0001671

Last edited: 2009-12-23 04:07

Mhmm. That works for me with libxml2 2.7.6, using the head of the 3.3 trunk (r2809):

xeval xml_generate(xml_parse("<abc/>") )
"<?xml version=\"1.0\"?>\n<abc/>\n"

Which version of libxml2 are you using?

Concerning 3.3.719: that is a valid version in Mantis which you can select - but only in the LDMud-3.3 project. ;-) Historically there are many version 3.3.x in the general LDMud project, but newer ones are created in the scope of LDMud-3.3. I transferred this issue now.

[edited to correct the libxml2 version]

Gnomi

2009-12-23 07:25

manager   ~0001672

I can't reproduce it either. Even with your binary from 0000709 I get "<?xml version=\"1.0\"?>\n<abc/>\n".

Wildcat

2009-12-23 08:51

reporter   ~0001673

Switching to iksemel caused it to not reproduce, from 709 my ldd is:
        linux-vdso.so.1 => (0x00007fff7bffe000)
        /lib64/rtkaio/librt.so.1 (0x00007f1b73cae000)
        libnsl.so.1 => /lib64/libnsl.so.1 (0x000000396b000000)
        libm.so.6 => /lib64/libm.so.6 (0x0000003969c00000)
        libcrypt.so.1 => /lib64/libcrypt.so.1 (0x000000396b400000)
        libssl.so.6 => /lib64/libssl.so.6 (0x000000325e200000)
        libcrypto.so.6 => /lib64/libcrypto.so.6 (0x000000325ce00000)
        libmysqlclient.so.15 => /usr/lib64/mysql/libmysqlclient.so.15 (0x000000325e600000)
        libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x0000003971000000)
        libz.so.1 => /usr/lib64/libz.so.1 (0x000000396a000000)
        libc.so.6 => /lib64/libc.so.6 (0x0000003969000000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003969800000)
        /lib64/ld-linux-x86-64.so.2 (0x0000003968c00000)
        libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 (0x000000325d200000)
        libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x000000325da00000)
        libcom_err.so.2 => /lib64/libcom_err.so.2 (0x000000396e400000)
        libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x000000325de00000)
        libdl.so.2 => /lib64/libdl.so.2 (0x0000003969400000)
        libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x000000325d600000)
        libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x000000396b800000)
        libresolv.so.2 => /lib64/libresolv.so.2 (0x000000396bc00000)
        libselinux.so.1 => /lib64/libselinux.so.1 (0x000000325ca00000)
        libsepol.so.1 => /lib64/libsepol.so.1 (0x000000396a800000)

from yum list | grep xml:
libxml2.i386 2.6.26-2.1.2.8 installed
libxml2.x86_64 2.6.26-2.1.2.8 installed
libxml2-devel.i386 2.6.26-2.1.2.8 installed
libxml2-devel.x86_64 2.6.26-2.1.2.8 installed
libxml2-python.x86_64 2.6.26-2.1.2.8 installed
(along with a few hundred other ones snipped)

zesstra

2009-12-23 11:34

administrator   ~0001674

Do you have a chance to try that with a recent release of libxml2? 2.6.26 was released in 2006, it may well be that this is caused by some incompatible changes in the lib.

Wildcat

2009-12-23 19:12

reporter   ~0001675

It's the latest version for centos 5.3:
yum install libxml2
Package libxml2-2.6.26-2.1.2.8.x86_64 already installed and latest version
Package libxml2-2.6.26-2.1.2.8.i386 already installed and latest version
Nothing to do

Given that switchign to iksemel caused the issue to be 'resolved' I'm loathe to change it on my production system and I keep my dev system on the same libs as prod. I'll see about spinning up a new VM though and trying it out but it'll probably not be for a few days.

zesstra

2010-02-15 18:04

administrator   ~0001732

Changing state to feedback for the meantime.

zesstra

2010-03-14 17:12

administrator   ~0001801

Closing for now, because we can't reproduce or debug it with the available information. I suspect an issue with the old libxml2.
If you have new info, please tell me to re-open.

Issue History

Date Modified Username Field Change
2009-12-22 20:33 Wildcat New Issue
2009-12-23 03:53 zesstra Project LDMud => LDMud 3.3
2009-12-23 04:05 zesstra Note Added: 0001671
2009-12-23 04:05 zesstra Status new => acknowledged
2009-12-23 04:05 zesstra Build => r2809
2009-12-23 04:06 zesstra Note Edited: 0001671
2009-12-23 04:07 zesstra Note Edited: 0001671
2009-12-23 07:25 Gnomi Note Added: 0001672
2009-12-23 08:51 Wildcat Note Added: 0001673
2009-12-23 11:34 zesstra Note Added: 0001674
2009-12-23 19:12 Wildcat Note Added: 0001675
2010-02-15 18:04 zesstra Note Added: 0001732
2010-02-15 18:04 zesstra Status acknowledged => feedback
2010-03-14 17:12 zesstra Note Added: 0001801
2010-03-14 17:12 zesstra Status feedback => closed
2010-03-14 17:12 zesstra Resolution open => unable to reproduce