Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!ucbvax!decwrl!sgi!kipp@warp.SGI.COM
From: kipp@warp.SGI.COM (Kipp Hickman)
Newsgroups: comp.sys.sgi
Subject: Re: -lmalloc
Summary: RE: -lmalloc
Message-ID: <25790@sgi.SGI.COM>
Date: 30 Jan 89 19:59:03 GMT
References: <4143@pt.cs.cmu.edu>
Sender: daemon@sgi.SGI.COM
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 13

In article <4143@pt.cs.cmu.edu>, scotts@isl1.ri.cmu.edu (Scott Safier) writes:
>  ...
> But there is also something strange with -lmalloc.  Sometimes,
> programs which execute perfectly with the bsd malloc, core dump when
> the other malloc is invoked.  For example, using X lib with bsd malloc
> is ok, but with lmalloc core dumps occur.

Most likely you have an Xlib which is compiled to allow malloc(0)'s.
-lmalloc does not support this ability.

					kipp hickman
					(kipp@sgi.com)
					silicon graphics inc.