From owner-freebsd-bugs Fri Dec 13 19:09:49 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA03027 for bugs-outgoing; Fri, 13 Dec 1996 19:09:49 -0800 (PST) Received: from george.lbl.gov (george-gs.lbl.gov [131.243.40.130]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id TAA03015 for ; Fri, 13 Dec 1996 19:09:44 -0800 (PST) Received: from portnoy.lbl.gov (portnoy.lbl.gov [131.243.2.11]) by george.lbl.gov (8.6.10/8.6.5) with ESMTP id TAA21828; Fri, 13 Dec 1996 19:09:17 -0800 From: "Jin Guojun[ITG]" Received: (jin@localhost) by portnoy.lbl.gov (8.6.10/8.6.5) id TAA09399; Fri, 13 Dec 1996 19:09:16 -0800 Date: Fri, 13 Dec 1996 19:09:16 -0800 Message-Id: <199612140309.TAA09399@portnoy.lbl.gov> To: bugs@freebsd.org, robert@nanguo.chalmers.com.au Subject: Re: Malloc bug report Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >The following is being reported in an attempt to track a Malloc problem. > >uname -a >FreeBSD nanguo.chalmers.com.au 2.2-961014-SNAP >FreeBSD 2.2-961014-SNAP #0: Wed Dec 4 19:45:06 EST 1996 >root@myname.my.domain:/usr/src/sys/compile/MYKERNEL i386 > > >problems >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. > >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. > > it then carries on and completes the process. > > >to reporduce; > >problem 1. Access index.html on the server root > >problem 2. do a fresh, new start up of tin. > If already run, remove the files .newnewsrc, .oldnewsrc, > and the directory .tin > >thanks >Robert Chalmers > >robert@chalmers.com.au >http://www.chalmers.com.au This is not a bug. It just warns that the program(s) try to free a pointer which has been freed or is not allocated by malloc/calloc. In 2.1.x or earlier, it was ignored or panic (I believe if in device driver). -Jin