This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author dhgutteridge
Recipients dhgutteridge
Date 2011-08-23.22:44:58
SpamBayes Score 0.000149188
Marked as misclassified No
Message-id <1314139504.06.0.542745003135.issue12829@psf.upfronthosting.co.za>
In-reply-to
Content
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 documentation bug open on this, see http://bugs.python.org/issue6676 -- a few other people made the same mistaken assumption as me.)  I found that given the right input, a segmentation fault occurs when one attempts to reuse the parser instance on more than one file.

The sample test case I've attached derives from what I'm using pyexpat for, which involves the parsing of Microsoft Office Open XML Excel files.  I found that the specific content in the initial file can influence whether the submission of subsequent files triggers a segmentation fault.

I'm reporting this against Python 2.7.2 on Mac OS X 10.6.8; it also occurs with Python 2.6.1 that's bundled with the OS.  I can also duplicate it on the development branch of NetBSD (my other development platform), specifically 5.99.47/amd64 with Python 2.6.7.
History
Date User Action Args
2011-08-23 22:45:04dhgutteridgesetrecipients: + dhgutteridge
2011-08-23 22:45:04dhgutteridgesetmessageid: <1314139504.06.0.542745003135.issue12829@psf.upfronthosting.co.za>
2011-08-23 22:45:03dhgutteridgelinkissue12829 messages
2011-08-23 22:45:02dhgutteridgecreate