httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <dgau...@arctic.org>
Subject Re: [STATUS] (apache-1.3) Fri May 1 23:45:24 EDT 1998
Date Mon, 04 May 1998 22:36:16 GMT
Maybe try disabling OPTIMIZE_TIMEOUTS if it's enabled on your platform... 
just a wild guess though.

Interesting though, ap_find_pool() is part of POOL_DEBUG, maybe there's a
bug in it.  sigh.

Dean

On Mon, 4 May 1998, Martin Kraemer wrote:

> On Sun, May 03, 1998 at 09:17:12PM -0700, Brian Behlendorf wrote:
> > By the way, I'm almost positive at this point that my core dumps were due
> > to using -O3 instead of just -O2 with gcc.  I'm now running with almost all
> > modules compiled in, and it's rock solid.
> 
> Hmmh. Then I'm the only one with regular (and *very* strange) core dumps.
>     [Fri May  1 21:14:26 1998] [notice] httpd: caught SIGSEGV, attempting to dump core
in /var/WWW/logs
>     [Fri May  1 21:14:41 1998] [notice] httpd: caught SIGSEGV, attempting to dump core
in /var/WWW/logs
>     [Fri May  1 21:15:30 1998] [notice] httpd: caught SIGSEGV, attempting to dump core
in /var/WWW/logs
>     [Fri May  1 21:17:09 1998] [notice] httpd: caught SIGSEGV, attempting to dump core
in /var/WWW/logs
>     [Fri May  1 21:18:55 1998] [notice] httpd: caught SIGSEGV, attempting to dump core
in /var/WWW/logs
>     [Fri May  1 21:19:14 1998] [notice] httpd: caught SIGSEGV, attempting to dump core
in /var/WWW/logs
>     [Fri May  1 21:21:40 1998] [notice] httpd: caught SIGABRT, attempting to dump core
in /var/WWW/logs
>     [Sat May  2 01:17:00 1998] [notice] httpd: caught SIGSEGV, attempting to dump core
in /var/WWW/logs
>     [Sat May  2 23:28:04 1998] [notice] httpd: caught SIGSEGV, attempting to dump core
in /var/WWW/logs
>     [Sun May  3 01:54:00 1998] [notice] httpd: caught SIGSEGV, attempting to dump core
in /var/WWW/logs
>     [Mon May  4 09:51:17 1998] [notice] httpd: caught SIGSEGV, attempting to dump core
in /var/WWW/logs
>     [Mon May  4 11:48:05 1998] [notice] httpd: caught SIGSEGV, attempting to dump core
in /var/WWW/logs
> This is a server with a very *low* traffic (so it has a chance to timeout
> once in a while). I still suspect timeouts to trigger the dumps.
> 
> I intrumented the core dump routine to call a debugger and print the
> stack trace, but all I get is:
> 
> sig_coredump(0xb, 0x0, 0x80479fc) at 0x807890d
> _sigacthandler
> address 0xffffffff is not mapped to this process
> 
> -or-
> 
> Ouch!  find_pool() called on pointer in a free block
> sig_coredump() at 0x807890d
> kill() at 0x80015594
> ap_find_pool() at 0x806e3ee
> ap_table_setn() at 0x806ed9a
> rename_original_env() at 0x807ff21
> internal_internal_redirect() at 0x8080015
> ap_internal_redirect() at 0x80800cd
> handle_dir() at 0x805f49a
> ap_invoke_handler() at 0x80718e8
> process_request_internal() at 0x807fdf2
> ap_process_request() at 0x807fe40
> child_main() at 0x8079d9d
> make_child() at 0x8079feb
> startup_children() at 0x807a07b
> standalone_main() at 0x807a466
> main(0x3, 0x8047efc, 0x8047f0c) at 0x807aafa
> _start() at 0x804a6bb
> 
> I don't know how to continue, as I don't know how to trigger the bug.
> The requested URIs are apparently unrelated to the bug.
> 
>     Martin
> -- 
> | S I E M E N S |  <Martin.Kraemer@mch.sni.de>  |      Siemens Nixdorf
> | ------------- |   Voice: +49-89-636-46021     |  Informationssysteme AG
> | N I X D O R F |   FAX:   +49-89-636-44994     |   81730 Munich, Germany
> ~~~~~~~~~~~~~~~~My opinions only, of course; pgp key available on request
> 


Mime
View raw message