Ethereal-dev: [Ethereal-dev] Compiling with -O3 crashes ethereal

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Thomas Reitelbach <tr@xxxxxxxxxxxxxxxx>
Date: Fri, 26 Dec 2003 22:55:10 +0100
Hello List,

i searched the mailing list archives and did not find any similar post.

A few days ago i compiled ethereal 0.10.0a. Unfortunately it always crashes 
either when i open a saved network dump (dumped using tethereal) or it 
crashes when i finish capturing.

It crashes with the following message on console:
** ERROR **: file ftypes.c: line 420 (fvalue_set): assertion failed: 
(fv->ftype->set_value)

I tried with Gtk 1.2.9 and Gtk 2.3, same problem on either.
After testing some other things i found that the crash is caused by my GCC 
optimization flags.
I'm using GCC 3.3.1 and compiled ethereal using "CFLAGS=-O3 -march=pentium3" 
and "CXXFLAGS=-O3 -march=pentium3". The configure commandline was 
"./configure --prefix=/usr --enable-gtk2 --enable-threads".
All libraries used by ethereal (pcap, gtk, whatever) are compiled with these 
GCC optimization flags as well.

Here comes the versioning output from ethereal:

tr:~$ ethereal -v
ethereal 0.10.0a
Compiled with GTK+ 2.3.0, with GLib 2.3.0, with libpcap 0.8, with libz 1.2.1,
with libpcre 4.4, without UCD-SNMP or Net-SNMP, without ADNS.
Running with libpcap version 0.8 on Linux 2.4.23

As this seems to be a problem when using GCC's optimization flags it may be 
advisable to not use them on ethereal. So now you're warned about this 
problem and can update the documenation or take whatever steps you might want 
to take :)

Hopefully this isn't old news for you ethereal-guys ;-)

Bye,
Thomas

-- 
Just because the message may never be received does not mean it is 
not worth sending.