Re: Memory profiling

"Alex R. Mosteo" <devnull@xxxxxxxxxxxxxx> writes:

> I suppose something similar can be achieved using distinct storage pools
> for each access type being tracked, but I find this more
> inconvenient. Ummm, maybe a type holding a list of storage pools created
> on demand...

All those storage pools can share the same underlying memory pool. That
is, each pool just keeps track of whatever debugging/statistics info you
want, and then calls some underlying pool, or just does a "new", or
calls malloc, or whatever. So gathering fine-grained (per type)
information does not need to imply that you have to actually allocate
type-segregated data.

- Bob
.