Guy:
A quick thanks for setting me straight. My diagnistoc tool now runs
perfectly on 64-bit.
Thanks.
TJ.
On Sat, 2007-08-11 at 16:34 +0100, TJ wrote:
> Guy, thanks so much for putting me straight!
> I doubt we'll be able to test the revised code in the diagnosis app on
> the 64-bit servers un
Guy, thanks so much for putting me straight!
It looks like the coding examples I'd been using to put together this
quick-n-dirty hack were flawed. I didn't have sufficient time to focus
on it but I was sure I was confused on the pointer-to-pointers bit - for
some reason when I'm tired I always get
TJ wrote:
I'm not sure if these leaks and losses are related to the SIGSEGV but
they certainly ought to be cleared up.
Yes, they should, and here's how you do it:
In your program, replace
pcap_if_t *this_dev;
pcap_if_t **alldevsp = &this_dev;
with
pcap_if_t *alldevs
Hello TJ,
The link to libpcap-valgrind.tar.bz2 does not seem to work, can you
please check it ?
Thanks,
Saikiran.
TJ wrote:
I've been working on analysing an issue with a cluster of Proliant
servers running Debian 2.6.18 64-bit with 4GB RAM on Xeon 3000 CPUs in a
data-centre.
As part of the
I've been working on analysing an issue with a cluster of Proliant
servers running Debian 2.6.18 64-bit with 4GB RAM on Xeon 3000 CPUs in a
data-centre.
As part of the diagnosis I have written a tool to check incoming
packets.
I've used the latest libpcap (0.9.7) built from source.
The tool is be
