|
From: tarun k. <tar...@ya...> - 2004-07-09 14:45:35
|
Steve, I am getting the same error too. I agree to you on that Valgrind 2.1.1 has bugs. If i run valgrind 2.1.1 with a --logfile=filename parameter, valgrnid segfaults. That's why i movoed back to the 2.0.0 version, but i still get the syscall error. Tarun Message: 2 From: Steven Dake <sd...@mv...> Reply-To: sd...@mv... To: val...@li... Organization: MontaVista Software, Inc. Date: Wed, 07 Jul 2004 14:06:56 -0700 Subject: [Valgrind-users] strangeness in valgrind 2.1.1 Folks I am using valgrind 2.1.1 to run the openais project (developer.osdl.org/dev/openais) through its paces. Its an excellent tool and I have already found a few errors. I am trying to sanitize all of the remaining errors and get an error that is: ==2834== Syscall param socketcall.recvmsg(msg.msg_iov[i] contains uninitialised or unaddressable byte(s) ==2834== at 0x3C111A16: sendmsg (socket.S:63) ==2834== by 0x8053371: message_handler_orf_token (gmi.c:2240) ==2834== by 0x8054779: recv_handler (gmi.c:3012) ==2834== by 0x8050876: poll_run (poll.c:458) ==2834== Address 0x3C182171 is 9 bytes inside a block of size 52 alloc'd ==2834== at 0x3C01D2CB: malloc (vg_replace_malloc.c:105) ==2834== by 0x8050AC7: gmi_pend_trans_item_store (gmi.c:501) ==2834== by 0x8050F59: gmi_mcast (gmi.c:669) ==2834== by 0x804A52F: clmNodeJoinSend (clm.c:323) I'm not quite sure how to read this message. It says "at sendmsg" but the syscall param is "socketcall.recvmsg". So which one is it? I have cleaned up all uninitialized variables that could possibly be related so I'm a little stuck as to what to do next to remove this error. Also, what does the "address X is 9 bytes insid ea block of size 52 alloced". does that tell where the iov[i] was allocated? --__--__-- __________________________________ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail |