From owner-freebsd-bugs Mon Oct 28 14:00:07 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA06540 for bugs-outgoing; Mon, 28 Oct 1996 14:00:07 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA06498; Mon, 28 Oct 1996 14:00:03 -0800 (PST) Date: Mon, 28 Oct 1996 14:00:03 -0800 (PST) Message-Id: <199610282200.OAA06498@freefall.freebsd.org> To: freebsd-bugs Cc: From: J Wunsch Subject: Re: bin/1916: List management bug in last, shows up with /etc/malloc.conf -> AJ Reply-To: J Wunsch Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR bin/1916; it has been noted by GNATS. From: J Wunsch To: davidn@sdev.usn.blaze.net.au Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/1916: List management bug in last, shows up with /etc/malloc.conf -> AJ Date: Mon, 28 Oct 1996 21:42:51 +0100 (MET) As David Nugent wrote: > Under some circumstances, last from -current dumps core. A sample The `some circumstances' are simply a "shutdown" entry. > wtmp file (uuencoded attached below) demonstrates the problem. > > >Description: > > A pointer is free(3)'ed, and subsequently used in the wtmp() function > in last.c. With MALLOC_OPTIONS set to AJ, the contents of the memory > pointed to by the free pointer are no longer valid, causing a core > dump. Sorry to say, but you're already too late. :) The problem has been reported in PR 1909, and fixed a couple of hours later... Needless to say, the fix looks damn similar to yours. -- 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. ;-)