Hi, In a Python XML application I have, an XPath query occasionally returns two matching nodes (which is wrong in my case) instead of one. This occurs at random times. I have submitted a bug report (# 228941), but that was closed due to the fact that I can't deliver a (stand-alone) program that reproduces the error. Some facts:
- It happens both with the libxml2 and lxml Python modules (the latter is not included with RHEL5, but I have rebuilt that from FC6). - The application works fine in RHEL4. - The application breaks at random places in RHEL5. - The application works fine in RHEL5 after I have upgraded libxml2 with version 2.6.27 from Fedora Core 6. My application parses a certain (static) XML file every time a certain object instance is created. It sometimes breaks the first time that an object is created, sometimes the 25th time, etc. If I run the same (deterministic) program twice, it breaks at different places (that is, it always breaks because the XPath query returns 2 nodes, while my programs asserts that at most one node is matched, but that error occurs at random times during the program run). I have now removed the assertion in my program and use only the first node of the result (the same node is returned twice when the error occurs!), but what worries me is that other XPath queries might result in errors I don't catch with an assert. This all sounds like a libxml2 bug, but I can't prove it. Are there any libxml2 users who also have problems with XPath on RHEL5 or maybe have some test program that can find these problems? Regards, -- -- Jos Vos <[EMAIL PROTECTED]> -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204 _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
