Received: (qmail 5155 invoked by uid 2012); 31 May 1999 03:25:58 -0000
Message-Id: <19990531032558.5154.qmail@hyperreal.org>
Date: 31 May 1999 03:25:58 -0000
From: Ben O'Shea <roady@linux-solutions.org>
Reply-To: roady@linux-solutions.org
To: apbugs@hyperreal.org
Subject: Apache/mod_php-3.0.7/mod_perl-1.19 segfault when accessing mod_perl document
X-Send-Pr-Version: 3.2

>Number:         4497
>Category:       mod_perl
>Synopsis:       Apache/mod_php-3.0.7/mod_perl-1.19 segfault when accessing mod_perl document
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          closed
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sun May 30 20:30:00 PDT 1999
>Last-Modified:  Fri Jul  9 10:10:32 PDT 1999
>Originator:     roady@linux-solutions.org
>Organization:
>Release:        1.3.6 (Unix)
>Environment:
Linux (RedHat 5.1) Kernel 2.0.35; gcc version 2.7.2.3;
>Description:
When accessing a mod_perl document the child segfaults under Apache/1.3.6+mod_php-3.0.7

backtrace results:

*(gdb) run -X -f /s101/current/config/apache/launch/ben-httpd.conf
Starting program: /a/apache_1.3.6/src/./httpd -X -f /s101/current/config/apache/launch/ben-httpd.conf

Program received signal SIGSEGV, Segmentation fault.
0x400d9992 in strrchr ()
(gdb) bt
#0  0x400d9992 in strrchr ()
#1  0xbfffeeec in ?? ()
#2  0x8223e2e in upper_digits.45 ()
Cannot access memory at address 0x1.
(gdb)

>How-To-Repeat:
Problem is only apparent with mod_perl and mod_php, and seems to only occur on
rhlinux 5.1 systems.
>Fix:

>Audit-Trail:
State-Changed-From-To: open-feedback
State-Changed-By: ask
State-Changed-When: Thu Jul  1 00:30:13 PDT 1999
State-Changed-Why:
Could you please try this again with the latest mod_perl and mod_php? I vaguely remember having heard about something similar with the version of mod_php you were using.

Please also remember to compile with DEBUG stuff enabled. 
State-Changed-From-To: feedback-closed
State-Changed-By: ask
State-Changed-When: Fri Jul  9 10:10:31 PDT 1999
State-Changed-Why:
[This is a standard response.]
No response from submitter, assuming issue has been resolved.
>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!     ]