recent bug reports...

["Lawrence A. Rowe" <Rowe@bmrc.berkeley.edu>]

hi -

Greg and Kun both reported problems that look like memory leaks and/or
access errors.  I think we all know this has been a problem with the
mash code for a long time.  The best way to locate/fix these problems is
to use one of the tools for locating these types of errors.  I did some
quick google searches and found a Linux program called memprof that
presents a GUI interface to data produced by modified libc allocation
routines that is reputed to be easy to use.

I think someone should volunteer to run this tool on vic, to start with,
to see if it can help us identify the memory leak.  BTW, Greg, have you
watched the memory size using task mgr while your long-term vic is
running?  It was very obvious that the Real Player had a memory leak
when I did that test.

Any volunteers?  Matt? Andrew Swan? Lloyd?
	Larry
-- 
Professor Lawrence A. Rowe          Internet:  Rowe@BMRC.Berkeley.EDU
Computer Science Division - EECS       Phone: 510-642-5117
University of California, Berkeley       Fax: 510-642-5615
Berkeley, CA 94720-1776            URL: http://bmrc.berkeley.edu/~larry