I am not sure what you mean, exactly. There are some other valgrind macros that need to be called for pointers other than the ones returned by 'malloc'. More importantly, the memory regions need to be marked as 'NOACCESS' after we are done using them from the pool allocator, or valgrind will complain; that's why I set them back to 'DEFINED' before writing to them in other functions.
This is my first time using valgrind, however, so I might just be confused about what you mean, and there is a simpler way of doing all this.
This is my first time using valgrind, however, so I might just be confused about what you mean, and there is a simpler way of doing all this.