#5354: after [5990] mod_python segfault on certain setups
-----------------------+----------------------------------------------------
Reporter: akaihola | Owner: adrian
Status: new | Component: Core framework
Version: SVN | Keywords: crash segfault
Stage: Unreviewed | Has_patch: 0
-----------------------+----------------------------------------------------
Changeset [5990] 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
{{{isValidHTML()}}} and {{{isWellFormedXml()}}} functions in
{{{django.core.validators}}}. Maybe these cases could be solved with other
tools?
--
Ticket URL: <http://code.djangoproject.net/ticket/5354>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
