Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache HTTPD Bugs Notification List" <bugs@httpd.apache.org>
From: bugzilla@apache.org
To: bugs@httpd.apache.org
Subject: DO NOT REPLY [Bug 36751]  -
    Apache + OpenSSL crashes while render mod_perl pages
Message-Id: <20050924143706.479FCDF@ajax.apache.org>
Date: Sat, 24 Sep 2005 16:37:06 +0200 (CEST)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=36751>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36751


jorton@redhat.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |NEEDINFO


------- Additional Comments From jorton@redhat.com  2005-09-24 16:37 -------
I'm confused, which is the stack backtrace *when the process crashes*?  

You have given two stack traces but then described how the code continues from
there, so neither of those stack traces are actually triggered by the crash?

> By the way, we configured and use the mod_perl filter functions. Once SSL 
> generate that error message, mod_perl calls 
>       MP_RUN_CROAK(modperl_output_filter_flush(filter),
>                     "Apache2::Filter");
> in modperl_run_filter(modperl_filter_t *filter) from modperl_filter.c, 
> which kills apache child process.

so what is the stack trace *when the child process is killed*?

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org