Re: [xml] xmlSchemaNewParserCtxt coredump




Sorry about creating this fuzz... I posted the original message based on another developers problem - tried it myself - and when setting the correct path to the vsd files I am not able to reproduce the problem any longer. The other person is on vacation for 4 weeks - I will have to wait until then to see if the problem is solved or not.

/Espen

Phone: +47 69215581 / + 47 92499076
email: espen ekeroth omxgroup com
MSN: espene halden net



Daniel Veillard <veillard redhat com>

04.08.2005 10:09
Please respond to veillard

       
        To:        Remy HAREL <rharel ext rd francetelecom com>
        cc:        Espen Ekeroth <espen ekeroth omxgroup com>, xml gnome org
        Subject:        Re: [xml] xmlSchemaNewParserCtxt coredump



On Thu, Aug 04, 2005 at 09:32:02AM +0200, Remy HAREL wrote:
> Daniel wants a small  source code which can help him reproducing this
> problem and see where it bugs.

 Actually no. I need a reproduceable test case based on xmllint.
The fact that xmlSchemaNewParserCtxt() crash may as well be due to
a heap corruption generated by other parts of their code or
an instance validation using a different schemas ...
 If the problem can be isolated to an schemas + an instance being
validated with xmllint, then it will be fixed quickly. If not,
there is no garantee, a standalone piece of code producing the
problem will be looked at but I don't want to debug other people
code, I have enough to do with mine.

Daniel

--
Daniel Veillard      | Red Hat Desktop team http://redhat.com/
veillard redhat com  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/



********************************************************************************
This e-mail and the information it contains may be privileged and/or
confidential. It is for the intended addressee(s) only.
The unauthorised use, disclosure or copying of this e-mail, or any information it contains, is prohibited.
If you are not an intended recipient, please contact the sender and delete the material from your computer.
********************************************************************************


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]