[Verse-dev] uninitialised data in v_n_send_data

[Emil Brink]

Samium Gromoff wrote:
> On Mon, 2006-04-03 at 11:01 +0200, peter Lunden wrote:
> 
>> I get the following printout when running my code in valgrind
>> (memory debugger)
>> 
>> ==9993== Syscall param socketcall.sendto(args) points to
>> uninitialised byte(s)
[...]
> I`m not exactly sure, but one legitimate reason for this probably is 
> packet padding bytes -- after all we probably do not want to waste
> cpu cycles initialising them.

There is no padding in Verse packets, so that's probably not it.

However, it's possible that the block is not *fully* initialized, since
it was not needed. I'm not quite sure how Valgrind treats that case,
although I've suspected that reason for such warnings, before.

I'd like to determine that, and/or fix the issue, programs that make
Valgrind keep quiet are nicer. Thanks for the reminder, Peter.

Regards,

/Emil