signal 10 in malloc call???

[Larry McVoy]

In article <3989 at killer.UUCP> toma at 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 at arizona.edu or ...!{uwvax,sun}!arizona.edu!lm