gnu, malloc, and "zero'd" memory

Article View: gnu.gcc.help

Article #52342

#52342

From: J. Eric Townsend
Date: Wed, 25 Nov 1992 10:51

15 lines
1164 bytes

In general, does GCC assume that memory returned by a malloc is set to
zeros?  In particular, does the stage1 build assume this?

I'm chasing down some wierd parse tree problems, probably caused by
the native compiler on my system being somewhat flaky.  It occurred to
me that perhaps the tree code expected "clean" memory and I'm not
giving it clean memory.

Comments?  Flames?

--
             J. Eric Townsend --  jet@nas.nasa.gov -- 415.604.4311
               '92 R100R, DoD# 0378, BMWOA, AMA, ACLU, EFF, CPSR
                                "HotHead Rules!"

Technical Details

Message-ID: <JET.92Nov25105140@boxer.nas.nasa.gov>

Path: arc1-ca.pugleaf.net!sparky!uunet!think.com!ames!data.nas.nasa.gov!data.nas.nasa.gov!jet

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 11318c,459b3f6402b4c06d,start
X-Google-Attributes: gid11318c,public
X-Google-ArrivalTime: 1992-11-25 11:19:26 PST
Newsgroups: gnu.gcc.help
Path: arc1-ca.pugleaf.net!sparky!uunet!think.com!ames!data.nas.nasa.gov!data.nas.nasa.gov!jet
From: jet@boxer.nas.nasa.gov (J. Eric Townsend)
Subject: gnu, malloc, and "zero'd" memory
Sender: news@nas.nasa.gov (News Administrator)
Organization: Numerical Aerodynamic Simulation, NASA Ames
Date: 25 Nov 92 10:51:40
Message-ID: <JET.92Nov25105140@boxer.nas.nasa.gov>
Distribution: gnu
Lines: 15