Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: chuck@morgan.com (Chuck Ocheret)
Newsgroups: comp.sys.sun
Subject: Re: "busted" malloc
Keywords: Software
Message-ID: <8902232040.AA10556@terminus.Morgan.COM>
Date: 8 Mar 89 20:07:33 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 11
Approved: Sun-Spots@rice.edu
Original-Date: Thu, 23 Feb 89 15:40:35 EST
X-Sun-Spots-Digest: Volume 7, Issue 188, message 5 of 22

One thing worth noting...

fprintf() may indirectly invoke malloc() (the stdio routines do this to
allocate buffer space) which can skew the results of malloc() tests.  If
you wish to examine malloc() results directly use an sprintf() followed by
write().  Or else use dbx.

+------------------+   Chuck Ocheret, Sr. Staff Engineer   +------------------+
| chuck@morgan.com |       Morgan Stanley & Co., Inc.      |  (212)703-4474   |
|   Duty now ...   |19th Floor, 1251 Avenue of the Americas| for the future.  |
+------------------+         New York, N.Y.  10020         +------------------+