|
From: Henrik N. <hn...@ma...> - 2004-04-19 07:48:22
|
On Mon, 19 Apr 2004, Banibrata Dutta wrote: > i thought that i'd not have to worry about it. well, actually i am > sure i don't have to do that, because in message finally sent out on > the wire, is composed by also looking at length of various parameters, > s.t. i do not really read any of the garbage octets. If valgrind warns on the syscall then there is octets within the sent message which has not been given any value. These octets may contain pretty much any value priorly used in the application or C library. Most often this will be 0, but not always. If you are positively sure all octets in the message should be set and there is no unset fields then you have a bug somewhere in how the message is created or in how it's length is calculated. Regards Henrik |