Daniel Berlin <[EMAIL PROTECTED]> writes: | On Sat, 2005-05-21 at 22:00 +0200, Gabriel Dos Reis wrote: | > Daniel Berlin <[EMAIL PROTECTED]> writes: | > | > [...] | > | > | > Parenthetically, I was wondering who is freeing those extensive | > | > regions of storage xmalloc/xcalloc()ed here and there? | > | | > | 1. The people who write the code to do the xmalloc'ing. | > | 2. Every couple of months, people run gcc through valgrind with leak | > | checking on to make sure we arne't leaking the xmalloc'd memory. | > | > If all memory is realized at the end of program, then obviously there | > is no leak, but that is not what I was looking for. | | Then what are you looking for?
[ A useful answer ;-) ] where the storage is returned/reused as soon as done, as opposed to waiting for the end of the compilation. [...] | > Do you know whether the have the resulst publically | > available somewhere? | No, i don't think anyone takes the extra effort to try to set up a web | page. Thanks, -- Gaby
