bin/92074: top(1) aborts in redzone

[Steven G. Kargl]

>Number:         92074
>Category:       bin
>Synopsis:       top(1) aborts in redzone
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jan 20 20:20:06 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Steven G. Kargl
>Release:        FreeBSD 7.0-CURRENT amd64
>Organization:
APL/UW
>Environment:
System: FreeBSD troutmask.apl.washington.edu 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Thu Jan 19 13:50:25 PST 2006 kargl at troutmask.apl.washington.edu:/usr/obj/usr/src/sys/SPEW amd64


	
>Description:
	
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.

>How-To-Repeat:

>Fix:



>Release-Note:
>Audit-Trail:
>Unformatted: