On Thu, Aug 6, 2009 at 1:50 PM, Bart Van Assche wrote:
> On Thu, Aug 6, 2009 at 12:02 PM,
>> Any opinions of whether this error could be causing my glibc double free
>> errors, or whether it is a red-herring?
>
> It is unlikely that the above message printed by Valgrind is related
> to the double f
Hi all,
In order for my program to send v3 traps (using snmptrap), I would like to
retrieve the user information, etc. from the snmpTargetParamsTable.
Unfortunately, this seems to be missing some important information like the
engine id and passphrase. Any idea where my program can get this i
2009/8/6 [email protected] :
> I inserted the memsets - and the valgrind error disapeared. Thanks for
> that - I will post this change on the patch tracker.
Don't bother - this fix has already been applied to the latest code
(as of early June) and should included in future releases.
Dave
s,
Craig
__ Information from ESET Smart Security, version of virus signature
database 4311 (20090806) __
The message was checked by ESET Smart Security.
http://www.eset.com
--
Let Crystal Reports h
On Thu, Aug 6, 2009 at 12:02 PM,
[email protected] wrote:
> The 1 remaining valgrind error (reproduced at the end in full) is
> complaining about
>
> "socketcall.sendmsg(msg.msg_control) points to uninitialised byte(s)".
Try to insert the statements "memset(&cmsg, 0, sizeof(cmsg));
memset(&m, 0
tes in 0 blocks.
==545== possibly lost: 128 bytes in 2 blocks.
==545==still reachable: 396,905 bytes in 8,266 blocks.
==545== suppressed: 0 bytes in 0 blocks.
==545== Rerun with --leak-check=full to see details of leaked memory.
__ Information from ESET Smart Security, v
