From owner-freebsd-stable Wed Mar 28 12:31:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from karon.dynas.se (karon.dynas.se [192.71.43.4]) by hub.freebsd.org (Postfix) with SMTP id 324C937B71D for ; Wed, 28 Mar 2001 12:31:36 -0800 (PST) (envelope-from mikko@dynas.se) Received: (qmail 78087 invoked from network); 28 Mar 2001 20:31:30 -0000 Received: from spirit.sto.dynas.se (HELO spirit.dynas.se) (172.16.1.10) by 172.16.1.1 with SMTP; 28 Mar 2001 20:31:30 -0000 Received: (qmail 9513 invoked from network); 28 Mar 2001 20:31:27 -0000 Received: from explorer.rsa.com (10.81.217.59) by spirit.dynas.se with SMTP; 28 Mar 2001 20:31:27 -0000 Received: (from mikko@localhost) by explorer.rsa.com (8.11.1/8.11.1) id f2SKVMV75614; Wed, 28 Mar 2001 12:31:23 -0800 (PST) (envelope-from mikko) Date: Wed, 28 Mar 2001 12:31:23 -0800 (PST) From: Mikko Tyolajarvi Message-Id: <200103282031.f2SKVMV75614@explorer.rsa.com> To: jon@rupture.net Cc: stable@freebsd.org Subject: Re: httpsd in free(): warning: chunk is already free. Newsgroups: local.freebsd.stable References: X-Newsreader: NN version 6.5.6 (NOV) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In local.freebsd.stable you write: >i'm running apache 1.3.19 on freebsd 4.3-RC cvsupped 03/23/01. apache >was built by hand with php4.0.4pl1 and apache_1.3.19+ssl_1.42. in the >parent server error log, i am getting thousands of the following >message: >httpsd in free(): warning: chunk is already free. >httpsd in free(): warning: chunk is already free. >occasionally it will say "page is already free." instead of chunk. >am i correct in assuming that this means httpsd uses freebsd's libc >and that the free() function from libc is reporting this warning >message? Yes. >how should i go about trying to fix it? it fills up my logfile >partition - yesterday i had a 730MB error_log. Your apache is buggy. Compile apache with debugging (-g), Run it with MALLOC_OPTIONS set to "A" (other combinations will likely catch even more bugs -- see malloc(3)). Apache should abort at the first occurence of an erroneous free(). Fire up a debugger and read the core file, figure out what the problem is, fix it. Iterate until there are no more errors. If you just percieve the problem as "getting lots of warnings in the log file," wish to ignore it and pretend that everything is peachy, you could probably wrap the apache startup with a script that redirects stderr to /dev/null before exec:ing apache, and pray that nothing bad will happen. $.02, /Mikko -- Mikko Työläjärvi_______________________________________mikko@rsasecurity.com RSA Security To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message