Hello and thanks first of all for your detailed reply. > What is the goal in integrating Valgrind with this scheme; that is, > what is not happening now which should be? For example checking whether the allocation function and its counter-part use the same tag. I thought it would be better to integrate it into an existing solution rather than writing my own that would then also point out call-stacks for the allocation code path.
> How is the tagged memory allocator obtaining the memory? > Is it not bootstrapped from some lower-level allocator which doesn't > know about the tags? Yes, ultimately from malloc. So I'm looking for a way to replace it, really. > The way to do this is to simply mark the meta-data unreadable > before returning the block of memory to the application, and > only opening/closing access to that meta-data when manipulating > it inside the allocator, using the VALGRIND_MAKE_MEM_DEFINED > and VALGRIND_MAKE_MEM_NOACCESS macros. > Fresh, uninitialized storage returned to the program (which the > program can write, but should not read) is set up using > VALGRIND_MAKE_MEM_UNDEFINED. Great, this is exactly the information I was looking for from looking at the headers and the manual. Thanks a lot, // Oliver ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
