You are viewing a plain text version of this content. The canonical link for it is here.

Posted to apache-bugdb@apache.org by Jason Clary <jc...@linuxbox.com> on 1997/12/07 07:31:59 UTC

mod_userdir/1524: access of /~ crashes with sigsegv

>Number:         1524
>Category:       mod_userdir
>Synopsis:       access of /~<login> crashes with sigsegv
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sat Dec  6 22:40:00 PST 1997
>Last-Modified:
>Originator:     jclary@linuxbox.com
>Organization:
apache
>Release:        1.2b3
>Environment:
Redhat 5
Linux version 2.0.32
gcc version 2.7.2.1
>Description:
SIGSEGV, but no core... and cores are enabled
>How-To-Repeat:
We had to take the server down and put an old version back.  If you e-mail me, I can put it back up on other ports long enough for you to see the problem.
>Fix:
not at the moment...  Haven't been able to trace it with no core.
%0
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]