Is there any support in memcheck for a client request to treat a block of
memory as read-only? I know memory can be defined as accessible/not accessible
or defined/undefined, but I don't see anything for "writable". It would be
really nice to be able to add client requests so that after a block of memory
is initialized, to be able to tell memcheck that certain bytes should never be
written again, because they have been initialized (e.g. pointer to another
object).
Phil
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
