tcpdump mailing list archives

Re: libpcap causing segmentation fault


From: Michael Richardson <mcr () sandelman ca>
Date: Tue, 14 Feb 2012 14:17:13 -0500


"Moshe" == Moshe Matitya <Moshe.Matitya () xconnect net> 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, we built libpcap 1.2.1 from the distribution tarball.
    Moshe> And yes, we are running it with libpcap 1.2.1 on RHEL 3.8 too
    Moshe> (without this problem). 

    Moshe> The kernel with CentOS 5.6 is 2.6.18-238.el5.
    Moshe> The kernel with RHEL 3.8 is 2.4.21-47.ELsmp.

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 years old.

My suggestion is to turn off (in the source code), any of the mmap
functionality, or at least printf() what is being used.   I would also
wonder if you are doing technology renewal, why you are stopping at
Centos 5, rather than 6 (or higher?) with a linux 3.0 kernel...

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr () sandelman ottawa on ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
                       then sign the petition. 

Attachment: _bin
Description:


Current thread: