On Tue, Aug 15, 2000, Henrik Nordstrom wrote:
> Well, that is a bad thing for the memPool accounting, but that is
> curently all. At least until memory pools are rewritten to handle blocks
> of allocated structures.
>
> Yes, it should be fixed.
>
> Btw, how do you detect the difference in xfree? All memPoolAlloc does it
> to return areas allocated with xcalloc(). It does not keep track of the
> allocated areas, only how much it has given out...
>
Oh? Hrm. I should re-read the mempool code. I thought it malloced a large
chunk of RAM and then dished out those like diskd handles SYSVSHM.
I might look at hacking in some code to track the allocations and the
allow me to find any abuse like this.
Adrian
Received on Tue Aug 15 2000 - 11:59:22 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:12:34 MST