Path: utzoo!attcan!uunet!snorkelwacker!usc!rutgers!mcnc!thorin!pooh!taylorr
From: taylorr@pooh.cs.unc.edu (Russell Taylor)
Newsgroups: comp.sys.sgi
Subject: Re: Bus error DURING call to malloc()
Keywords: help bus error malloc
Message-ID: <14652@thorin.cs.unc.edu>
Date: 13 Jun 90 13:08:02 GMT
References: <14525@thorin.cs.unc.edu> <1990Jun10.211156.16153@calgary.uucp> <789@ki.UUCP> <10822@medusa.cs.purdue.edu>
Sender: news@thorin.cs.unc.edu
Reply-To: taylorr@pooh.cs.unc.edu (Russell Taylor)
Organization: University Of North Carolina, Chapel Hill
Lines: 9


	I traced the problem down by using the Saber-C product we recently
got for our Suns.  The problem (as many people responded) was that I was
doing strange things to memory that had been gotten via calls to malloc().
	The Saber-C environment checked for the strangeness and showed me
right where it was happening.  Once I fixed it, the problem went away.
	Thank you all for your suggestions!

	Russell Taylor