GNOME Bugzilla – Bug 661838
Segmentation error validating document against OOXML schema
Last modified: 2021-07-05 13:22:20 UTC
Created attachment 199058 [details] an archive containing all files used in the test I believe this needs to be fixed urgently. .docx is one of the worlds largest XML document formats and inability to validate if not already, soon will no doubt become a huge problem - it is for our business that I can say for sure Steps to getting the bug ------------------------ 1. created a simple MS word .docx file 2. extracted the document.xml file from the .docx and renamed it to a_test.xml 3. downloaded the ecma-375 (3rd) transitional OOXML schema 4. successfully validate a_test.xml file against the schema in XMLspy 5. tried to validate the document on CentOS 5.7 in PHP 5.3 6. there were a few items about the schema PHP didn't like (these didn't worry XMLspy) eg. xml:space - so I made a few minor amendments to the ecma schema 7. When these minor changes were made and PHP validation rerun, the validation "disappeared" with no error 8. PHP team said probably an xmllib2 problem - and suggested I test with xmllint 9. I ran the command xmllint --noout --schema ./wml.xsd ./a_test.xml ....and the core dump happened Additional notes ----------------------- - This problem occurs identically on Centos 6.0 (libxml2 2.7.6 x64) and CentOS 5.7 - I have attached all files used in the test - to reproduce simply extract to a folder and run the same xmllint command - To find out a bit more information about the bug I ran the same command again with --debugent switch and the below is what was returned $ xmllint --debugent --noout --schema ./wml.xsd ./a_test.xml new input from file: ./wml.xsd new input from file: dml-wordprocessingDrawing.xsd new input from file: dml-main.xsd new input from file: shared-relationshipReference.xsd new input from file: shared-commonSimpleTypes.xsd new input from file: dml-diagram.xsd new input from file: dml-chart.xsd new input from file: dml-chartDrawing.xsd new input from file: dml-picture.xsd new input from file: dml-compatibility.xsd new input from file: dml-lockedCanvas.xsd dml-wordprocessingDrawing.xsd:9: element import: Schemas parser warning : Element '{http://www.w3.org/2001/XMLSchema}import': Skipping import of schema located at 'wml.xsd' for the namespace 'http://schemas.openxmlformats.org/wordprocessingml/2006/main', since this namespace was already imported with the schema located at './wml.xsd'. new input from file: shared-math.xsd shared-math.xsd:9: element import: Schemas parser warning : Element '{http://www.w3.org/2001/XMLSchema}import': Skipping import of schema located at 'wml.xsd' for the namespace 'http://schemas.openxmlformats.org/wordprocessingml/2006/main', since this namespace was already imported with the schema located at './wml.xsd'. new input from file: xml.xsd new input from file: xmlspec.xsd new input from file: xlink.xsd new input from file: shared-customXmlSchemaProperties.xsd Segmentation fault (core dumped)
This is a really really critical problem for our business. Is there any way someone could provide some sort of feedback as to the timeline for looking at this? thanks very much
I'm becoming very nervous about this - our business has committed to PHP and we are now stuck between the PHP team who say "not our problem - it's libxml, follow up directly with them" And libxml who as can be seen above don't appear to have anyone actually monitoring these bugs. Is there anything I can do to help expedite this? PS - as a PHP user I disagree entirely with the PHP team approach explained above. If a PHP command fails for some reason, the PHP team should in my opinion be chasing it down - not the PHP userbase
well, after the fantastic response effort I saw here I went out and purchased Saxonica ...and it just works [and what excellent support - I highly recommend the product]
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/libxml2/-/issues/ Thank you for your understanding and your help.