Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ll-xn!husc6!necntc!necis!mrst!sdti!mjy
From: mjy@sdti.UUCP
Newsgroups: comp.unix.questions,comp.unix.wizards,comp.unix.xenix
Subject: Re: smail2.5
Message-ID: <135@sdti.UUCP>
Date: Fri, 2-Oct-87 12:53:10 EDT
Article-I.D.: sdti.135
Posted: Fri Oct  2 12:53:10 1987
Date-Received: Sun, 4-Oct-87 06:36:48 EDT
References: <398@auscso.UUCP> <132@sdti.UUCP> <29699@sun.uucp>
Reply-To: mjy@sdti.UUCP (0000-Michael J. Young)
Organization: Software Development Technologies, Sudbury MA
Lines: 14
Keywords: smail Xenix trouble
Xref: utgpu comp.unix.questions:3915 comp.unix.wizards:4314 comp.unix.xenix:773

In article <29699@sun.uucp> guy%gorodish@Sun.COM (Guy Harris) writes:
>Is it that malloc(3X) is buggy, or that it's SVID-compliant?

No, it's buggy.  The core dumps come from within malloc(3x) itself.
Microport is aware of the problem, but they don't seem to be anxious to
fix it.  I don't think they even plan on fixing it in their next release
(2.3).  They just say, "Workaround: Try using malloc(3c)".  They must
be understaffed.  Doesn't sound like that hard a problem to fix.  It's
certainly easy to duplicate the symtoms :-).
-- 
Mike Young - Software Development Technologies, Inc., Sudbury MA 01776
UUCP     : {decvax,harvard,linus,mit-eddie}!necntc!necis!mrst!sdti!mjy
Internet : mjy%sdti.uucp@harvard.harvard.edu
Tel      : +1 617 443 5779