Re: [Valgrind-users] Accessing memory marked as UNDEFINED

2010-07-20 Thread Bert Wesarg
On Tue, Jul 20, 2010 at 12:29, WAROQUIERS Philippe wrote: > > >>> On Mon, Jul 19, 2010 at 6:41 PM, Bert Wesarg >> 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_UN

Re: [Valgrind-users] Accessing memory marked as UNDEFINED

2010-07-20 Thread WAROQUIERS Philippe
>> On Mon, Jul 19, 2010 at 6:41 PM, Bert Wesarg > 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

Re: [Valgrind-users] Accessing memory marked as UNDEFINED

2010-07-19 Thread Bart Van Assche
On Mon, Jul 19, 2010 at 6:41 PM, Bert Wesarg 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 d

Re: [Valgrind-users] Accessing memory marked as UNDEFINED

2010-07-19 Thread Bert Wesarg
On Mon, Jul 19, 2010 at 18:51, Bart Van Assche wrote: > On Mon, Jul 19, 2010 at 6:41 PM, Bert Wesarg > 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

[Valgrind-users] Accessing memory marked as UNDEFINED

2010-07-19 Thread Bert Wesarg
Hi all, 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 pointe