Path: utzoo!mnetor!uunet!husc6!think!ames!ncar!noao!arizona!lm
From: lm@arizona.edu (Larry McVoy)
Newsgroups: comp.unix.wizards
Subject: Re: signal 10 in malloc call???
Message-ID: <5360@megaron.arizona.edu>
Date: 6 May 88 09:27:32 GMT
References: <3989@killer.UUCP>
Reply-To: lm@megaron.arizona.edu (Larry McVoy)
Organization: University of Arizona, Tucson
Lines: 14
Keywords: sys V rel 3.1, died in malloc?

In article <3989@killer.UUCP> toma@killer.UUCP (Tom Armistead) writes:
>I've been having an *interesting* thing happen under System 5, release 3.1
>Unix, on a 3b2/310 and was wondering if I could get any insight from
>any one as to the problem (or cause of)???

I dunno if this is it or not, but I have found out (the hard way) that malloc
keeps info in the memory it allocates (actually: is about to allocate).  The
bottom line is that if you overrun a malloced area you will cause crashes that
seem to stem from inside the malloc lib itself.  My problems occured on a
Vax running 4.3+NFS.
-- 
	"Peace and Unity - Neon Prophet, Tucson AZ"

Larry McVoy	lm@arizona.edu or ...!{uwvax,sun}!arizona.edu!lm