On Sun, Jan 14, 2001 at 09:59:56PM +0000, Minko Markov wrote:
> 0.8.15 compiled smoothly. I installed and tried it. The main
> window opened. I clicked Capture->Start->OK . So far, so good.
> There was no network traffic at the moment. When I clicked
> "Stop", the program aborted with the message:
>
> ** ERROR **: file libpcap.c: line 763 (libpcap_read_header): should not be reached
> aborting...
It may have produced a core dump file. If so, please send us a stack
trace, as per the "How to Report a Bug" instructions in the README file.
If it didn't produce a core dump, the changes are that unless somebody
can reproduce the problem (the problem doesn't happen for me, and I
don't have any flavor of Red Hat Linux, and don't plan on upgrading the
libc on my Debian partition, so the chances that I will be able to
reproduce it are essentially nil).
> Then I tried another test, this time with some traffic (ping).
> This time ethereal aborted at Capture->Start->OK :
>
> ** ERROR **: file libpcap.c: line 1024 (libpcap_dump): should not be reached
> aborting...
>
> [1]+ Aborted ethereal
It may have produced a core dump file. If so, please send us a stack
trace, as per the "How to Report a Bug" instructions in the README file.
> Sure, these two messages refer to wiretap/libpcap.c . I have no idea what
> they mean.
They mean that something that shouldn't have happened happened.
> The third problem with 0.8.15 is that, when I click Edit->Preferences,
> it dies immeadiately with "Segmentation fault", without core dump.
No core dump? Make sure you run it as yourself, not as root, in a
directory in which you have write permission.
If you can't do that, run it inside GDB.
> Since after the previous install (the successful one) of 0.8.14
> I have upgraded glibc from 2.1.3 to 2.2. Can that be the problem?
It could well be. Replacing individual pieces of your OS runs the risk
of causing all sorts of weird failures, especially if it's as critical a
component as the C library.
What happens if you just install the binary RPMs?
