Re: [Valgrind-users] Using memcheck to treat memory as read-only

[John R. <jr...@Bi...>]

> 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).

No; "read only" is not one of the states in the current memory accounting info.