-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash on _xmlfree on Windows #1
Comments
would you please post the code that led to the crash? |
I do not have the code at hand (and the windows machine...) but I can generate a minimal example next week. The code works fine on linux and I am pretty sure that it is the "tri_xmlfree" function as the code works, when I change this function to do nothing. |
Here on windows it crashes on: using LightXML when I remove _xmlfree(p) from _xcopystr(p::Xstr) in clib.jl everything works. Using xmlFree instead of libc free does also crash Julia. |
I'm guessing the following errors fall under the same category:
but I don't yet have the knowledge to peek under the hood and verify it's the same |
There is a comment next to However, the libxml2 manual is quite clear that xmlFree should be used: "It's up to the caller to free the memory with xmlFree()." : http://www.xmlsoft.org/html/libxml-tree.html#xmlNodeGetContent ... This certainly smells NQR. |
Hard to say whether @digital-carver's errors are at all related here, but I suspect the "tests" referred to in the comment in b33d030 were not run on windows. We should probably try using the libxml2 xmlFree instead. |
Hi,
This is really a great package!
Still, I have to report one bug I have on windows. The complete Julia shell crashes when I call e.g. the content function. I have traced it down to the tri_xmlfree(p) function.
Do you have any idea or should this got to the Julia bug tracker as it seems to be not related to LightXML.
I use a windows dll of libxml2 to get this work.
P.S.: using MiniXML in Readme.md should be propably using LightXML
The text was updated successfully, but these errors were encountered: