george@iguanodon.cis.ohio-state.edu (George M. Jones) (02/23/89)
Under UMAX 4.2 when calling share(2) with a first argument of 0, are you guarenteed that the resulting memory region will be zero filled (assuming of course that the call succeeds) ? The man page does not say anything about this either way, but a quick test program indicates that the memory is zero filled. P.S. Thanks to everyone who replied to my earlier question about malloc(3). Seems that the fast but not so efficient Berkeley malloc algorithm explained the behavior that I was seeing (grabbing memory in power of two size chunks, but also adding on "just a few" bytes, making it impossible for one malloc to get more than half the "limit). Thanks, ---George Jones -=- OSU Computer & Inf. Science 2036 Neil Ave.,Columbus,Ohio 43210. 614-292-7325 george@cis.ohio-state.edu or ...!osu-cis!george May the Christmas gifts of Love and Joy be with you always.