[issue6676] expat parser throws Memory Error when parsing multiple files

David H. Gutteridge added the comment: Updating to reflect the Python 3.4 documentation is now also relevant to this discussion. Perhaps someone could commit a change something like my suggestion in msg143295? -- versions: +Python 3.4 ___ Python

[issue12829] pyexpat segmentation fault caused by multiple calls to Parse()

David H. Gutteridge added the comment: Okay. I'd seen the earlier issue, but had submitted this separately because I wasn't sure if it was a security-related bug, whereas the older issue didn't mention anything of the sort. (In retrospect, I could'

[issue6676] expat parser throws Memory Error when parsing multiple files

David H. Gutteridge added the comment: Ned: My proposed wording is: "Note that only one document can be parsed by a given instance; it is not possible to reuse an instance to parse multiple files." To provide more detail, one could also add something like: "The isfinal argume

[issue12829] pyexpat segmentation fault caused by multiple calls to Parse()

David H. Gutteridge added the comment: Further details: - The original test case I'd submitted crashed on the development branch of NetBSD as well as Mac OS X Snow Leopard, but not the most recent stable branch of NetBSD. I've found a separate test case that crashes on both b

[issue12829] pyexpat segmentation fault caused by multiple calls to Parse()

David H. Gutteridge added the comment: Confirming that Python 3.2.1 crashes the same way on Mac OS X 10.6.8: Process: Python [9594] Path: /Library/Frameworks/Python.framework/Versions/3.2/Resources/Python.app/Contents/MacOS/Python Identifier: Python Version

[issue12829] pyexpat segmentation fault caused by multiple calls to Parse()

David H. Gutteridge added the comment: Terry: I wasn't aware xml.parsers.expat is deprecated, though it clearly says so in the documentation, I now see... (I'd been using it because it features prominently in various examples in Python books, and it's lightweight.) I have

[issue6676] expat parser throws Memory Error when parsing multiple files

David H. Gutteridge added the comment: The documentation should definitely be updated to clarify that a parser instance is not reusable with more than one file. I had a look at the equivalent documentation for Perl and TCL, and Perl's implementation explicitly does not allow attemp

[issue12829] pyexpat segmentation fault caused by multiple calls to Parse()

David H. Gutteridge added the comment: Here's the (non-debug) trace under OS X: Process: Python [4604] Path: /Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python Identifier: Python Version: ??? (???) Code Type:

[issue12829] pyexpat segmentation fault caused by multiple calls to Parse()

David H. Gutteridge added the comment: I believe this may be an OS-specific bug somehow, albeit one that affects multiple OSes. I cannot duplicate the crash on NetBSD 5.1_STABLE/i386 with Python 2.6.7, or on OpenSuSE 11.3 with Python 2.6.5. (It's interesting that it doesn't cr

[issue12829] pyexpat segmentation fault caused by multiple calls to Parse()

New submission from David H. Gutteridge : I stumbled across this bug because of a misunderstanding I had about how the pyexpat module works. I'd inferred that a given instance could be reused to parse multiple files, which is apparently not supported. (There's already a documen