Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Sender: trawick@bellsouth.net
To: new-httpd@apache.org
Subject: Re: apache 2.0 on apache.org status
References: <Pine.BSF.4.31.0101312132590.729-100000@localhost>
From: Jeff Trawick <trawickj@bellsouth.net>
Date: 01 Feb 2001 08:14:54 -0500
In-Reply-To: Brian Behlendorf's message of "Wed,
 31 Jan 2001 21:35:45 -0800 (PST)"
Message-ID: <m3g0hyfstt.fsf@adsl-77-241-65.rdu.bellsouth.net>
Lines: 34
User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Brian Behlendorf <brian@collab.net> writes:

> apache 2.0 built as of this afternoon now running on apache.org.  A few
> corefiles so far in /usr/local/apache2/corefiles, but less frequent than
> before.  Looks like at least 2-3 different problems.

Problem two looks like this (example: httpd.core.8)

#0  0x28149964 in isatty () from /usr/lib/libc.so.4
(gdb) bt
#0  0x28149964 in isatty () from /usr/lib/libc.so.4
#1  0x28149d49 in free () from /usr/lib/libc.so.4
#2  0x281363b2 in closedir () from /usr/lib/libc.so.4
#3  0x808c8ac in dir_cleanup (thedir=0x81f31f4) at dir.c:68
#4  0x808832e in run_cleanups (c=0x81f3fdc) at apr_pools.c:625
#5  0x808842b in apr_clear_pool (a=0x81f800c) at apr_pools.c:729
#6  0x8088487 in apr_destroy_pool (a=0x81f800c) at apr_pools.c:758
#7  0x806d997 in ap_process_http_connection (c=0x81300ec) at connection.c:255
#8  0x806d77c in ap_run_process_connection (c=0x81300ec) at connection.c:85
#9  0x806d904 in ap_process_connection (c=0x81300ec) at connection.c:221
#10 0x8064500 in child_main (child_num_arg=209) at prefork.c:1052
#11 0x8064631 in make_child (s=0x80b4514, slot=209, now=981005281) at prefork.c:1124
#12 0x8064838 in perform_idle_server_maintenance () at prefork.c:1267
#13 0x8064bb1 in ap_mpm_run (_pconf=0x80b400c, plog=0x80de00c, s=0x80b4514) at prefork.c:1455
#14 0x806931c in main (argc=3, argv=0xbfbffa6c) at main.c:431
#15 0x8058401 in _start ()

I don't know why free() would call isatty(), but perhaps it is a weird
path (i.e., error path) caused by memory corruption?  Maybe we called
closedir() twice for same data?  Just a silly idea...
-- 
Jeff Trawick | trawickj@bellsouth.net | PGP public key at web site:
       http://www.geocities.com/SiliconValley/Park/9289/
             Born in Roswell... married an alien...