From: "Oliver Hartkopp" <oliver@hartkopp.net>
To: nhorman@tuxdriver.com
Cc: netdev@vger.kernel.org
Subject: dropwatch for network drop monitor
Date: Fri, 17 Apr 2009 14:57:24 +0200 (MEST) [thread overview]
Message-ID: <200904171257.n3HCvOba029938@post.webmailer.de> (raw)
Hi Neal,
i tried the dropwatch app from your git.
Compiling the source produces:
hartko@vwagwolkf320:~/dropwatch/src$ make
gcc -c -g main.c
gcc -c -g lookup.c
gcc -c -g lookup_bfd.c
gcc -c -g lookup_kas.c
lookup_kas.c: In function lookup_kas_cache:
lookup_kas.c:56: warning: cast from pointer to integer of different size
lookup_kas.c: In function lookup_kas_proc:
lookup_kas.c:100: warning: cast from pointer to integer of different size
lookup_kas.c:103: warning: cast from pointer to integer of different size
gcc -g -o dropwatch main.o lookup.o lookup_bfd.o lookup_kas.o -lbfd -lreadline -lnl
You cast a 'pc' variable to __u64 - is your code depending on 64 bit ??
Starting the stuff brings:
vwagwolkf320:/home/hartko/dropwatch/src# ./dropwatch
Initalizing kallsyms db
dropwatch> start
Enabling monitoring...
Waiting for activation ack....
Waiting for activation ack....
Waiting for activation ack....
Waiting for activation ack....
Waiting for activation ack....
Waiting for activation ack....
Failed activation request, error: Operation now in progress
Shutting down ...
vwagwolkf320:/home/hartko/dropwatch/src#
And in my kernel log i get at the same time:
[ 7070.568482] netlink: 60 bytes leftover after parsing attributes.
Any ideas?
Oliver
next reply other threads:[~2009-04-17 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 12:57 Oliver Hartkopp [this message]
2009-04-17 13:28 ` dropwatch for network drop monitor Neil Horman
2009-04-17 14:16 ` Oliver Hartkopp
2009-04-17 14:30 ` Neil Horman
2009-04-17 17:22 ` Neil Horman
2009-04-17 18:13 ` Oliver Hartkopp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200904171257.n3HCvOba029938@post.webmailer.de \
--to=oliver@hartkopp.net \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).