Hello,
I am trying to run Valgrind on a FreeBSD 8.0 system with a Myri ethernet
card. My application uses libpcap to capture packets. Myri card has its
own snf ( Sniff )and libpcap libraries. I am able to run valgrind
without this card on my local machine. But when i run it on the system
with myri card i get errors and it does not work. The error states that
a function is not implemented. I guess the problem is about shared
libraries. My application uses shared libraries and the application
binary points right libraries as i check with ldd tool. There are some
warnings about system calls too. There is also an error about semaphores.
I would be happy if anybody can show me a workaround for this.
Are there any similar tools for FreeBSD to find memory leaks. I am
trying to find a memory leak in my application.
Myri structure:
http://www.myricom.com/scs/SNF/doc/index.html
ldd output:
libsnf.so.0 => /usr/local/opt/snf/lib/libsnf.so.0 (0x8006d7000)
libpcap.so.1 => /usr/local/opt/snf/lib/libpcap.so.1 (0x8007e1000)
libssl.so.6 => /usr/lib/libssl.so.6 (0x800911000)
libglib-2.0.so.0 => /usr/local/lib/libglib-2.0.so.0 (0x800a63000)
libxml2.so.5 => /usr/local/lib/libxml2.so.5 (0x800c43000)
libc.so.7 => /lib/libc.so.7 (0x800ea8000)
libz.so.5 => /lib/libz.so.5 (0x8010e4000)
libthr.so.3 => /lib/libthr.so.3 (0x8011f9000)
libcrypto.so.6 => /lib/libcrypto.so.6 (0x801311000)
libintl.so.9 => /usr/local/lib/libintl.so.9 (0x8015ab000)
libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x8016b5000)
libpcre.so.0 => /usr/local/lib/libpcre.so.0 (0x8018b3000)
libm.so.5 => /lib/libm.so.5 (0x8019f9000)
Valgrind output:
==32264== Warning: noted but unhandled ioctl 0x20004d01 with no
size/direction hints
This could cause spurious value errors to appear.
See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper
wrapper.
Warning: noted but unhandled ioctl 0x20004d05 with no size/direction hints
This could cause spurious value errors to appear. See
README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper.
Warning: noted but unhandled ioctl 0x20004d0d with no size/direction
hints This could ca
snf.0 P (userset) SNF_BOARDNUM = 0
snf.0 P (environ) SNF_NUM_RINGS = 10 (0xa)
snf.0 P (environ) SNF_RSS_FLAGS = 1 (0x1)
snf.0 P (default) SNF_DATARING_SIZE = 268435456 (0x10000000)
(256.0 MiB)
snf.0 P (userset) SNF_FLAGS = 257 (0x101)
snf.0 P (default) SNF_TIMESYNC_INTERVAL = 2000 (0x7d0)
snf.0 P (environ) SNF_DEBUG_MASK = 3 (0x3)
snf.0 P (default) SNF_DEBUG_FILENAME = stderr
snf.0 P SNF_DEBUG_MASK=0x3 for modes WARN=0x1, PARAM=0x2 QSTATS=0x4
TIMESYNC=0x8 IOCTL=0x10 QEVENTS=0x20
snf.0 P SNF lib version : 1.5.1
snf.0 P SNF lib build : [email protected] Thu Jul 21 14:02:41 EDT 2011
360dce652
snf.0 P SNF kernel version: 1.5.1
snf.0 P SNF kernel build : [email protected] Thu Jul 21 14:02:41 EDT 2011
360dce652
snf.0 P kwindow [ 0x52000.. 0x53000) size 4
KiB 4096 (0x1000)
snf.0 P rx_flow_cntrs [ 0x53000.. 0x54000) size 4
KiB 4096 (0x1000)
snf.0 P desc_ring [ 0x23200000.. 0x23a00000) size 8
MiB 8388608 (0x800000)
snf.0 P shared_data [ 0x39a33000.. 0xec2e5000) size 2856
MiB 2995462144 (0xb28b2000)
snf.0 P data_ring [ 0xdc2e5000.. 0xec2e5000) size 256
MiB 268435456 (0x10000000)
snf.0 P vring_state [ 0x39a33000.. 0x39a35000) size 8
KiB 8192 (0x2000)
snf.0 P vring_descq [ 0x39a35000.. 0x3c235000) size 40
MiB 41943040 (0x2800000)
snf.0 P vring_dataq [ 0x3c235000.. 0xdc2d5000) size 2560
MiB 2685009920 (0xa00a0000)
use spurious value errors to appear.
See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper
wrapper.WARNING: unhandled syscall: 405
--32264-- You may be able to write your own handler.
--32264-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--32264-- Nevertheless we consider this a bug. Please report
--32264-- it at http://valgrind.org/support/bug_reports.html.
*sem_open of snf_rsem:0 failed, errno = 78
2011-10-05 09:41:04: [32264] ERROR: tcpip_open_live: libtcpip: couldn't
open device itap0: itap0: snf_open failed: Function not implemented*
==32264==
==32366== Warning: noted but unhandled ioctl 0x20004d01 with no
size/direction hints
This could cause spurious value errors to appear.
See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper
wrapper.
Warning: noted but unhandled ioctl 0x20004d05 with no size/direction hints
This could cause spurious value errors to appear.
See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper
wrapper.
Warning: noted but unhandled ioctl 0x20004d0d with no size/direction hints
This could casnf.0 P (userset) SNF_BOARDNUM = 0
snf.0 P (environ) SNF_NUM_RINGS = 10 (0xa)
snf.0 P (environ) SNF_RSS_FLAGS = 1 (0x1)
snf.0 P (default) SNF_DATARING_SIZE = 268435456 (0x10000000)
(256.0 MiB)
snf.0 P (userset) SNF_FLAGS = 257 (0x101)
snf.0 P (default) SNF_TIMESYNC_INTERVAL = 2000 (0x7d0)
snf.0 P (environ) SNF_DEBUG_MASK = 3 (0x3)
snf.0 P (default) SNF_DEBUG_FILENAME = stderr
snf.0 P SNF_DEBUG_MASK=0x3 for modes WARN=0x1, PARAM=0x2 QSTATS=0x4
TIMESYNC=0x8 IOCTL=0x10 QEVENTS=0x20
snf.0 P SNF lib version : 1.5.1
snf.0 P SNF lib build : [email protected] Thu Jul 21 14:02:41 EDT 2011
360dce652
snf.0 P SNF kernel version: 1.5.1
snf.0 P SNF kernel build : [email protected] Thu Jul 21 14:02:41 EDT 2011
360dce652
snf.0 P kwindow [ 0x52000.. 0x53000) size 4
KiB 4096 (0x1000)
snf.0 P rx_flow_cntrs [ 0x53000.. 0x54000) size 4
KiB 4096 (0x1000)
snf.0 P desc_ring [ 0x23200000.. 0x23a00000) size 8
MiB 8388608 (0x800000)
^C2011-10-05 09:41:07: [32222] SYSTEM: SHUTDOWN signal caught, starting
shutdown procedures...
2011-10-05 09:41:07: [32222] SYSTEM: PID 32222 [parent: 21187]: exited
with code: 0, uptime: 7 seconds
2011-10-05 09:41:07: [32222] SYSTEM: sending TERM signal to worker pid 32366
2011-10-05 09:41:07: [32366] SYSTEM: SHUTDOWN signal caught, starting
shutdown procedures...
==32222==
~/leaktest/itap/code/inseptra]# 2011-10-05 09:41:07: [32366] SYSTEM:
worker PID 32366 [parent: 1]:
exiting with code: 0; has been up for 2 seconds.
use spurious value errors to appear. See
README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
