From owner-freebsd-current@FreeBSD.ORG Fri Jan 20 20:05:08 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99E1C16A41F; Fri, 20 Jan 2006 20:05:08 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 329BC43D8B; Fri, 20 Jan 2006 20:04:59 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by kane.otenet.gr (8.13.4/8.13.4/Debian-8) with SMTP id k0KK4vQA008078; Fri, 20 Jan 2006 22:04:58 +0200 Received: by flame.pc (Postfix, from userid 1001) id ED50C118D8; Fri, 20 Jan 2006 22:04:49 +0200 (EET) Date: Fri, 20 Jan 2006 22:04:49 +0200 From: Giorgos Keramidas To: Steve Kargl Message-ID: <20060120200449.GB94172@flame.pc> References: <20060120193620.GA26029@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060120193620.GA26029@troutmask.apl.washington.edu> Cc: freebsd-current@freebsd.org, jasone@freebsd.org Subject: Re: top(1) aborts in redzone X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2006 20:05:08 -0000 On 2006-01-20 11:36, Steve Kargl wrote: > 75 processes: 5 running, 70 sleeping > CPU states: 98.3% user, 0.0% nice, 1.7% system, 0.0% interrupt, 0.0% idle > Mem: 586M Active, 1202M Inact, 200M Wired, 20K Cache, 214M Buf, 9752M Free > Swap: 17G Total, 17G Free > > top: (malloc) Corrupted redzone 1 byte after 0x2020056f0 (size 1975) (0x0)D > Abort (core dumped) 1 132 0 295M 257M RUN 0 5:07 93.95% scat > troutmask:kargl[202] 132 0 295M 257M RUN 0 5:02 93.26% scat > > The above happened as I was resizing an xterm with an > actively run top(1). This is on amd64 with malloc.c > v 1.100. Can you file a bug report please? I will look into this, as I can reproduce it here, but I don't want it to be forgotten or lost in list-noise. Thanks in advance :)