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. But, it is nice to know that people run GCC through valgrind every couple of months. Do you know whether the have the resulst publically available somewhere? -- Gaby
