Wireshark · Ethereal-users: [Ethereal-users] Re: Strange behaviour ethereal 0.9.0 (self compiled) capture file corrupted !!]

[pigi@xxxxxxxx]

>> Must say that if I download the binary package from slackware it works
>> correctly.
>> ethereal -v say:
>
> What does the Ethereal in the binary package from Slackware report with
> "ethereal -v" and "ldd ethereal"?
>
Here we are:

/usr/bin/ethereal -v
ethereal 0.9.0, with GTK+ 1.2.10, with GLib 1.2.10, with libpcap 0.6, with
libz 1.1.3, without SNMP

ldd /usr/bin/ethereal
        libcrypto.so.0 => /usr/lib/libcrypto.so.0 (0x40017000)
        libgtk-1.2.so.0 => /opt/gnome/lib/libgtk-1.2.so.0 (0x400e1000)
        libgdk-1.2.so.0 => /opt/gnome/lib/libgdk-1.2.so.0 (0x40206000)
        libgmodule-1.2.so.0 => /opt/gnome/lib/libgmodule-1.2.so.0
(0x40238000)
        libglib-1.2.so.0 => /opt/gnome/lib/libglib-1.2.so.0 (0x4023b000)
        libdl.so.2 => /lib/libdl.so.2 (0x4025e000)
        libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x40263000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40270000)
        libm.so.6 => /lib/libm.so.6 (0x40327000)
        libz.so.1 => /usr/lib/libz.so.1 (0x40349000)
        libc.so.6 => /lib/libc.so.6 (0x40358000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

> Then it has nothing to do with the version of libpcap, as we don't use
> libpcap to read capture files.
I was sure :-)

>> But it is what happening. If I save the "corrupted" using the
>> "libpcap" format the next capture is OK.
>
> That still doesn't mean that there's a default reading format in
> Ethereal.
Absolutely, I was just explaining the behaviour.

>
> It means that the code to read capture files is somehow broken on the
> particular system you're using, perhaps due to problems in the system
> library.  It works fine on a number of other systems.

Ok, but why the difference between "live update" and "not live update" ?

Anyway the behaviour is the same as Andrew J.Gavin

Thx
Pigi