>> On Mon, Jul 19, 2010 at 6:41 PM, Bert Wesarg ><[email protected]> wrote: >>> >>> I would have expected, that when I do a read access on a memory >>> location (ie. dereference the pointer), which was previously marked >>> with VALGRIND_MAKE_MEM_UNDEFINED(), I get an error message from the >>> memcheck tool. But I don't. I also don't get an error, when I do a >>> read access on a pointer freshly returned from malloc(). I
I think that if you use VALGRIND_MAKE_MEM_NOACCESS that you should get an error message as soon as you dereference. Philippe ____ This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. Any views expressed in this message are those of the sender. ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
