Huber, George K RDECOM CERDEC STCD SRI wrote: > Well we have not put anything in that memory location yet, and > as I recall, under Linux any memory is zero-out when returned by malloc to > help prevent information leakage from one application to another.
Memory contains zeroes when it is first given to the process by the kernel. Whether or not memory returned from malloc() contains zeroes depends upon whether that memory has been used previously by the current process. At the beginning of a process' life cycle (e.g. at the top of main()), memory returned from malloc() is likely to contain zeroes. As time goes by, it becomes increasingly likely that memory returned from malloc() has previously been allocated, used, then free()d. In which case, the memory's contents will have been retained; neither malloc() nor free() themselves fill the memory with zeroes. If you need to ensure that memory contains zeroes, either use calloc() (which is defined to fill the memory with zeroes), or fill it yourself with memset(). -- Glynn Clements <[EMAIL PROTECTED]> - To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
