www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alessandro Bottoni <abott...@quadrante.com>
Subject general/8286: Segmentation fault and core dump when using mod_rewrite and mod_so
Date Mon, 03 Sep 2001 14:21:38 GMT

>Number:         8286
>Category:       general
>Synopsis:       Segmentation fault and core dump when using mod_rewrite and mod_so
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Sep 03 07:30:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     abottoni@quadrante.com
>Release:        1.3.20
>Organization:
apache
>Environment:
- Red Hat 7.1 (fresh, "virgin" installation, with all modules) on a Dell Optiflex GX150 (PIII,
128Mb RAM).
- ezPublish installer 1.0 (see below)
>Description:
You get a segmentation fault and, sometime, a core dump when you try to start the HTTPd. You
could get a "segmentation fault" line in the error.log, too.

I detected this problem while tring to install "ezPublish" (see http://developer.ez.no), by
using its bash installer, on a new Red Hat 7.1 machine. ezPublish installs a second copy of
the HTTPd, beside the one installed by RH7.1, and configure it for using virtual hosts and
rewrite rules. ezPublish uses both mod_so and mod_rewrite, already suspected to produce this
kind of problem (see Report #4577, #6204 and #8205).

ezPublish installer could give a good opportunity to reproduce those bugs and study them.
>How-To-Repeat:
- make a fresh install of Red Hat 7.1
- install ezPublish 2.1 by using it bash installer 1.0 (see http://developer.ez.no)
- start the HTTPd installed by ezPublish (/opt/ezpublish/apacheXXXX/bin/httpd). 
>Fix:
I did not find any workaround.
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]
 
 


Mime
View raw message