|
From: <e1-...@em...> - 2003-10-10 15:35:54
|
Hi,
Valgrind-20030725 gives me the following output when I run my program through it:
==23303== Thread 5:
==23303== Syscall param socketcall.setsockopt(optval) contains uninitialised or unaddressable byte(s)
==23303== at 0x420E8472: setsockopt (in /lib/i686/libc-2.2.5.so)
==23303== by 0x8066488: set_pcap_filter__13LwxCdbHandler (CdbHandler.cc:367)
==23303== by 0x806631E: open_pcap__13LwxCdbHandler (CdbHandler.cc:331)
==23303== by 0x8065CB3: __13LwxCdbHandlerPC6StringUi18LwxIfEffectiveType (CdbHandler.cc:140)
==23303== by 0x8054119: handle_new_if__9IfHandlerP9IfhIfInfo (ifhandler.cc:767)
==23303== by 0x8053550: compare_if_list_diffs__9IfHandler (ifhandler.cc:432)
==23303== by 0x8052F0F: if_loop__9IfHandler (ifhandler.cc:232)
==23303== by 0x8052C06: pthread_if_loop (ifhandler.cc:159)
==23303== by 0x4026E6C3: thread_wrapper (vg_libpthread.c:667)
==23303== by 0x40174943: (within /usr/local/lib/valgrind/valgrind.so)
==23303== Address 0x41BC4CFE is on thread 5's stack
My program is written in C++, and what you are seeing are the demangled symbols. Also, my program is using the well-known "pcap" library for low level packet handling.
(other programs that use libpcap seem to exhibit this problem as well).
Question: how do I suppress this error in my logs? I can't seem to figure out the right incantation to get Valgrind to ignore this error. My best guess so far is this:
{
this_is_just_a_comment
Addrcheck,Memcheck:Param
socketcall.setsockopt(optval)
fun:set_pcap_filter__13LwxCdbHandler
fun:open_pcap__13LwxCdbHandler
fun:*
}
I have to confess that I don't totally understand the syntax of Valgrind's suppression file format yet.
Thanks for any help!
--kevin
|
|
From: Nicholas N. <nj...@ca...> - 2003-10-10 15:46:38
|
On Fri, 10 Oct 2003 e1-...@em... wrote: > Question: how do I suppress this error in my logs? I can't seem to > figure out the right incantation to get Valgrind to ignore this error. See FAQ #17 N |