Re: [tcpdump-workers] libpcap causing segmentation fault

2012-02-15 Thread Michael Richardson
> "Moshe" == Moshe Matitya writes: Moshe> Could you give me any pointers as to what I need to do in the Moshe> code to turn off mmap functionality? There was a message a few weeks ago about this from Guy. The archives should be on gmane and other places. -- ] He who is tired

Re: [tcpdump-workers] libpcap causing segmentation fault

2012-02-15 Thread Moshe Matitya
On Tuesday, February 14, 2012 9:17 PM, Michael Richardson wrote: > >That's a significant jump in functionality. >I don't think 2.4 had any memory mapped functionality at all. > >If 2.6.18 has any (redhat likes to backport all sorts of things), the >question becomes... does it work? 2.6.18 is 5 y

Re: [tcpdump-workers] libpcap causing segmentation fault

2012-02-14 Thread Guy Harris
On Feb 14, 2012, at 6:09 AM, Moshe Matitya wrote: > Yes, we built libpcap 1.2.1 from the distribution tarball. ...so it's presumably 64-bit. - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.

Re: [tcpdump-workers] libpcap causing segmentation fault

2012-02-14 Thread Michael Richardson
> "Moshe" == Moshe Matitya writes: >> Whose libpcap 1.2.1 are you using? >> I assume that it is one that you built. On RHEL 3.8 were you using >> libpcap 1.2.1? >> >> Also can you tell us what kernels are in each, as RHEL 3.8 was a long >> time ago. Moshe> Yes,

Re: [tcpdump-workers] libpcap causing segmentation fault

2012-02-14 Thread Michael Richardson
Whose libpcap 1.2.1 are you using? I assume that it is one that you built. On RHEL 3.8 were you using libpcap 1.2.1? Also can you tell us what kernels are in each, as RHEL 3.8 was a long time ago. -- ] He who is tired of Weird Al is tired of life! | firewalls [ ] Michael Ri

Re: [tcpdump-workers] libpcap causing segmentation fault

2012-02-14 Thread Moshe Matitya
andelman.ca [mailto:m...@sandelman.ca] Sent: Tuesday, February 14, 2012 3:57 PM To: tcpdump-workers@lists.tcpdump.org Cc: Moshe Matitya Subject: Re: [tcpdump-workers] libpcap causing segmentation fault Whose libpcap 1.2.1 are you using? I assume that it is one that you built. On RHEL 3.8 were you using

Re: [tcpdump-workers] libpcap causing segmentation fault

2012-02-14 Thread Moshe Matitya
On Tuesday, February 14, 2012 3:40 PM, ri...@happyleptic.org wrote: > >Calling pcap_loop() after it returned something else than 0? No, pcap_loop() is called only once. Moshe - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.

Re: [tcpdump-workers] libpcap causing segmentation fault

2012-02-14 Thread rixed
-[ Tue, Feb 14, 2012 at 03:26:21PM +0200, Moshe Matitya ] > Any ideas as to what may be causing this would be much appreciated. Calling pcap_loop() after it returned something else than 0 ? - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.

[tcpdump-workers] libpcap causing segmentation fault

2012-02-14 Thread Moshe Matitya
We are running an application using libpcap 1.2.1, on CentOS 5.6 (64-bit), on a machine with a 10 gigabit NIC. We have been using this application for several years, using previous versions of libpcap, previous versions of Linux, and other NIC's, without any problems. Also, the current version