|
From: Eric E. <eri...@fr...> - 2004-08-24 21:37:43
|
In fact there is only one warning. What you see is 2 stacks: - the one where the error occured (when calling someto) - the one where the memory block involved in the error was allocated Either Valgrind is broken (could you give the version you are using ?), or your code is doing wrong, e.g. : - classic memset( p, 0, sizeof(p) ) instead of sizeof( *p ) - or you passed a wrong len or buf argument to sendto Cheers -- Eric Tom Hu wrote: > Hi, > > It looks like there are two warning here, > First one is syscall param socketcall.sendto. I initialized "msg" > parameter with memset zero in xxx_data_to_packet [please see the second > section] and it still post the warning. Can anyone help why? |