rouault opened a new pull request #39: URL: https://github.com/apache/xerces-c/pull/39
when a OutOfMemory exception occurs. Spotted by https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=39127 (on GDAL) The commits are a bit in increasing order of triviality. The ownership rules of ContentSpecNode first and second members, as used by ComplexTypeInfo, are super complex. shared_ptr would be much welcome here! I can just tell that valgrind on my test case reports no double-free nor memory leak after those fixes.... By the way what is the C++11 story of Xerces and the potential use of unique_ptr, shared_ptr ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
