[Valgrind-users] What would be the best approach to make Valgrind understand tagged memory?

[Oliver S. <ol...@f-...>]

Hi,

several systems use tagged memory to identify blocks of memory used by 
the same code and similar. What would be the best way of telling 
Valgrind about this custom allocation scheme? The "Memory Pools" don't 
seem to cover the possibility of tagged memory, as they only take 
parameters similar to malloc() itself.

Tagged memory comes in several flavors and in some cases it is important 
to pass the same tag to the counterpart of the allocation function as 
was given at the time of allocation. Therefore dropping the tag isn't an 
option either.


Thanks in advance,

// Oliver