From owner-freebsd-bugs Sat Dec 14 00:55:15 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA17196 for bugs-outgoing; Sat, 14 Dec 1996 00:55:15 -0800 (PST) Received: from irz401.inf.tu-dresden.de (irz401.inf.tu-dresden.de [141.76.1.12]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id AAA17191 for ; Sat, 14 Dec 1996 00:55:12 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz401.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA29439; Sat, 14 Dec 1996 09:55:05 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA00297; Sat, 14 Dec 1996 09:53:49 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id JAA23737; Sat, 14 Dec 1996 09:43:57 +0100 (MET) From: J Wunsch Message-Id: <199612140843.JAA23737@uriah.heep.sax.de> Subject: Re: Malloc bug report To: robert@nanguo.chalmers.com.au (Robert Chalmers) Date: Sat, 14 Dec 1996 09:43:57 +0100 (MET) Cc: bugs@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612140143.LAA02969@nanguo.chalmers.com.au> from Robert Chalmers at "Dec 14, 96 11:43:06 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Robert Chalmers wrote: > The following is being reported in an attempt to track a Malloc problem. ...but you're reporting it to the wrong group of people. :) > The malloc warnings I have found are > > 1) in the httpd's error.log. Both Apache, and NSCA httpd procuce the > same warning, which is > Malloc warning: free():page already free. > This warning is produced each time the file called 'index.html' > is accessed. It may be produced by others, but certainly this > file produces the warning in the error.log file. This kind of malloc warnings is generally an indication about bugs in the application using malloc(), not about a problem in malloc() itself. So if you can reproduce that problem, send it (along with a page that lets you reproduce it) to the Apache maintainers. Of course, you should first make sure that you're running the most recent version of Apache, since it's not unlikely that they've already fixed that problem. > 2) in the 'tin' newsreader, when it _first_ starts, and is setting up > its files; it produces, > Malloc warning: free():junk pointer, to high to make sense. Same here. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)