home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.aix
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!ux1.cso.uiuc.edu!news.cso.uiuc.edu!void.ncsa.uiuc.edu!marca
- From: marca@void.ncsa.uiuc.edu (Marc Andreessen)
- Subject: Re: SUMMARY: dbx problems
- References: <OINK.92Jul26033741@julian.newshost.uwo.ca>
- Message-ID: <Brzn1v.7oG@news.cso.uiuc.edu>
- Sender: usenet@news.cso.uiuc.edu (Net Noise owner)
- Organization: University of Illinois at Urbana
- Date: Sun, 26 Jul 1992 08:46:42 GMT
- Lines: 24
-
- oink@newshost.uwo.ca (Test Account) writes:
- : In article <BrvAFJ.6oM@news.cso.uiuc.edu> marca@void.ncsa.uiuc.edu (Marc Andreessen) writes:
- :
- : I believe). Also, 3.1 malloc would clear all memory it allocated to 0;
- : 3.2 malloc does not. (Normally, malloc isn't supposed to do this -
- : but calloc is.)
- :
- : My experience has shown that this is simply not true. Although it probably is
- : true of malloc()ed memory from the heap, it is certainly NOT true of recently
- : free()ed amd re-malloc()ed memory.
-
- Yargh, you're right. Never miiiiiiiiind...
-
- : Certainly not something to count on!
-
- Absolutely...
-
- Marc
-
- --
- Marc Andreessen
- Software Development Group
- National Center for Supercomputing Applications
- marca@ncsa.uiuc.edu
-