Red Hat Bugzilla – Bug 467246
python-tidy: the bindings are not 64bit safe
Last modified: 2008-10-30 08:50:13 EDT
Description of problem:
The tidy python bindings aren't 64bit safes and cause segmentation faults under Apache/mod_python or Apache/mod_wsgi.
Version-Release number of selected component (if applicable):
Everytime that a mod_python (or mod_wsgi) script is executed.
Steps to Reproduce and Patch:
See the following tickets:
Created attachment 320563 [details]
Fixes the pointer truncation
This one-line patch fixes the pointer truncation and works for me in both 32 and 64 bit systems.
Changed the platform to x86_64 (but it mostly likely affects other 64bit systems)
One of the tidy maintainers also mentions an interface change that was made in 2006 that hasn't been synced into utidylib (the utidylib code is from 2004).
See the Arnaud's comments in the sourceforge tidy ticket mentioned above.
Bug report against utidylib:
* [ Bug #14691 ] bindings aren't 64bit safe
python-tidy-0.2-4.fc9 has been submitted as an update for Fedora 9.
python-tidy-0.2-4.fc8 has been submitted as an update for Fedora 8.
Thanks for the nice report!
Thanks for the new package release.
I still haven't looked up much into the 2006 tidy interface change
mentioned in the sourceforge ticket. Nevertheless I believe the "sinkData" field of the class _OuputSink needs to be modified (most likely to ctypes.POINTER(ctypes.c_void_p) )
The messages in comments #5 and #6 are misleading: the new python-tidy packages have been submitted for *update testing* and not for update.
python-tidy-0.2-4.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
python-tidy-0.2-4.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.