Return-Path: Delivered-To: apmail-perl-modperl-archive@www.apache.org Received: (qmail 43844 invoked from network); 4 Sep 2009 23:11:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Sep 2009 23:11:45 -0000 Received: (qmail 27708 invoked by uid 500); 4 Sep 2009 23:11:43 -0000 Delivered-To: apmail-perl-modperl-archive@perl.apache.org Received: (qmail 27654 invoked by uid 500); 4 Sep 2009 23:11:43 -0000 Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list modperl@perl.apache.org Received: (qmail 27645 invoked by uid 99); 4 Sep 2009 23:11:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Sep 2009 23:11:43 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [200.4.195.166] (HELO m1.aasa.com.pe) (200.4.195.166) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Sep 2009 23:11:34 +0000 Received: from [172.16.0.92] (lima92.aasa.com.pe [172.16.0.92]) by m1.aasa.com.pe (8.12.11.20060308/8.12.10/SuSE Linux 0.7) with ESMTP id n84NBC0I003379 for ; Fri, 4 Sep 2009 18:11:12 -0500 Subject: Trivial changes to the Apache configuration result in segfaults for TWiki (installed as a mod_perl based application) From: Rafael Caceres To: modperl@perl.apache.org Content-Type: text/plain Date: Fri, 04 Sep 2009 18:17:25 -0500 Message-Id: <1252106245.4857.9.camel@rcaceres.aasa.com.pe> Mime-Version: 1.0 X-Mailer: Evolution 2.24.1.1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hello All, I'm having a very strange problem with a mod_perl application: TWiki. Unrelated changes to the httpd.conf like adding an Alias or an Location section, or even adding or removing a comment result in segfaults in that application. Other applications, either cgi or Apache::Registry based applications keep working with no problem. Also unnafected is our mod_perl based Single Sign On. Has anyone seen something like this before? Rafael