From 89fef7837416b626b828c0dfec1c247f69d6f9ca Mon Sep 17 00:00:00 2001 From: Jeff Trawick Date: Sat, 2 Jun 2001 00:22:19 +0000 Subject: [PATCH] mention another problem experienced on daedalus using 2_0_16 git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@89257 13f79535-47bb-0310-9956-ffa450edef68 --- STATUS | 21 +++++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) diff --git a/STATUS b/STATUS index 39071b3e68f..f206f68602d 100644 --- a/STATUS +++ b/STATUS @@ -1,5 +1,5 @@ APACHE 2.0 STATUS: -*-text-*- -Last modified at [$Date: 2001/05/25 20:04:47 $] +Last modified at [$Date: 2001/06/02 00:22:19 $] Release: @@ -22,7 +22,7 @@ DAEDALUS 2.0 PROBLEMS: * mod_cgid and suexec have a problem co-existing. suexec sees a null command string sometimes. - * core dump from 20010418 + * core dump from 20010418 running 2_0_16 /usr/local/apache2b/corefiles/httpd.core.2 #0 0x2813a3c8 in kill () from /usr/lib/libc.so.4 @@ -62,6 +62,23 @@ DAEDALUS 2.0 PROBLEMS: but zero bytes sent. Presumably the FreeBSD kernel sendfile() did the same thing (not 100% sure). + * core dump from 20010521 and 20010529 running 2_0_16 - the "3030" problem + + /usr/local/apache/corefiles/httpd.core.6 + #0 0x80987e8 in apr_cvt (arg=1.3980432860952889e-76, + ndigits=808464432, decpt=0x30303030, + sign=0x30303030, eflag=808464432, + buf=0x30303030
) at apr_snprintf.c:177 + #1 0x30303030 in ?? () + Cannot access memory at address 0x30303030. + + In both coredumps the request is /server-status?auto. + + It is unclear whether the apr_*printf function was passed bad + data or it screwed up on its own. 0x30 is '0'. There is a + string of 200-300 '0' characters in the dump, apparently + overlaying enough of the stack to cause serious problems :) + RELEASE SHOWSTOPPERS: WARNING: ALWAYS check srclib/apr/STATUS and srclib/apr-util/STATUS -- 2.47.2