> Sometimes this message is caused by uninitialized padding bytes. If
> you don't find the cause via source reading, you can check the data
> passed to the system call sendmsg() via the
> VALGRIND_CHECK_MEM_IS_DEFINED() client request. See also the header
> file /usr/include/valgrind/memcheck.h for more information.

Thanks for the tip.

So in general "Address 0xNNNNN is X bytes inside a block of size Y
alloc'd" is just some info message, right? I just don't understand
completely why I may need it...

-- 
Best regards, Pavel

------------------------------------------------------------------------------
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to