django imports minidom (which imports pyexpat) causing a modpython segfault on certain setups
|Reported by:||Antti Kaihola||Owned by:||Adrian Holovaty|
|Cc:||gkelly@…||Triage Stage:||Design decision needed|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Changeset  introduces and uses the
django.utils.version.get_svn_revision() function which uses minidom.parse(). With certain combinations of Apache and mod_python versions, the version mismatch of
libexpat used by both of them causes an Apache crash (segmentation fault on Linux). Apparently the problem has been worked around in Python 2.5.
For the inexperienced mod_python user this problem can be really hard to track down, since the symptoms are just empty web pages from the server and segmentation faults with no additional explanation in the Apache error log.
Would it be wise to avoid using
minidom to avoid potential frustration for new users who might have a problematic setup?
Currently minidom is only used in
get_svn_revision() and the
isWellFormedXml() functions in
django.core.validators. Maybe these cases could be solved with other tools?
Change History (10)
comment:1 Changed 9 years ago by
|Patch needs improvement:||unset|
comment:6 Changed 9 years ago by
|Summary:||after  mod_python segfault on certain setups → django imports minidom (which imports pyexpat) causing a modpython segfault on certain setups|
|Triage Stage:||Unreviewed → Design decision needed|