validity of free() on later pointer operations
Akira Takiguchi
akira at atson.asahi-np.co.jp
Thu Jul 12 14:38:40 AEST 1990
In article <1956 at runxtsa.runx.oz.au> edward at runxtsa.runx.oz.au (Edward Birch) writes:
|I quote the manual here:
| The argument to "free" is a pointer to a block previosly allocated
| by "malloc"; after "free" is performed this space is made available
| for further allocation, but its contents are left undisturbed.
|
|The above manual entry implies that the following is correct although
|*strongly* unadvisible.
It seems to me that the manual warns about the possibility of a
security breach when you leave sensitive data in the free'ed space.
--
Akira Takiguchi @ ATSON, Inc.
More information about the Comp.lang.c
mailing list