RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 734365 [details]
Script to produce the traceback.

python-lxml fails on 32bit machines but works correctly on 64bit machines.  I've attached a script and input file that can reproduce the error.

I ran the script against python-lxml-2.2.3-1.1.el6 and also against lxml from PyPI (in a virtualenv).  The former failed and the later succeeded.  I'm not sure what the root cause is.

python-lxml is one of the most widely used python libraries, making this a more urgent bug than not.

Created attachment 734370 [details]
Input for the test script

This is a known problem - bug #874546.
We haven't been able to find a cause yet.

In python-lxml 3.2.3 this problem is already fixed in upstream.
However, RHEL-6 is using version 2.2.3, where the problem is a bit different and thus solving it was a bit tricky.
I finally found out the cause of the bug: after whole xml file is read and last iteration is performed, iteration is not stopped (for some strange reason) and it tries to iterate further, causing an exception. I fixed this and attached a patch.

Created attachment 788441 [details]
A patch that should fix the iterparse exception issue

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

*** Bug 1109095 has been marked as a duplicate of this bug. ***