Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!iuvax!purdue!krk
From: krk@cs.purdue.EDU (Kevin Kuehl)
Newsgroups: comp.sys.sgi
Subject: Re: Bus error DURING call to malloc()
Keywords: help bus error malloc
Message-ID: <10822@medusa.cs.purdue.edu>
Date: 12 Jun 90 20:43:45 GMT
References: <14525@thorin.cs.unc.edu> <1990Jun10.211156.16153@calgary.uucp> <789@ki.UUCP>
Reply-To: krk@cs.purdue.edu (Kevin Kuehl)
Organization: Computing About Physical Objects
Lines: 16

In article <789@ki.UUCP> dwatts@ki.UUCP (Dan Watts) writes:
>in other places in the code and try to find the _bad_ code by seeing which
>ones work, and which ones die (note to free() the malloc()'d mem just

Another thing you can do (if you are fortunate enough to have access
to a Sun4) is to use the `malloc_debug(2)' on a Sun4.  This is one of
the greatest tools I have ever used.   On every call to malloc, it
checks the heap and verifies that it is not corrupted.  If it is
corrupted, the program dumps core so you can find it.

This would be great to have under Irix, don't you think?  Whatd'ya say
at SGI?  I would really appreciate this feature.

Kevin
krk@cs.purdue.edu
..!{decwrl,ucbvax,gatech}!purdue!krk