Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Ethereal-dev: [Ethereal-dev] Persistent Ethereal crashes: line 431 (fvalue_set): assertion fai

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

Date: Wed, 7 Jul 2004 15:33:17 -0500
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



When I run Ethereal, it always crashes at the point when it's going to
display the first packet with this error:
** ERROR **: file ftypes.c: line 431 (fvalue_set): assertion failed: (fv->ftype->set_value)
aborting...

If I select "Update list of packets in real time", it crashes as soon
as the first packet appears.

If I don't select "Update list of packets in real time", it crashes
as soon as I click "Stop" in the window that counts packets.

I see this behavior regardless of what sort of packets I'm capturing,
and I also see this behavior when I try to read captured packets from
a file.

As for what I'm using:
  # ethereal -v
  ethereal 0.10.4
  Compiled with GTK+ 2.4.2, with GLib 2.4.2, with libpcap 0.8.3, with libz 1.2.1,
  with libpcre 4.5, with Net-SNMP 5.1.1, with ADNS.
  Running with libpcap version 0.8.3 on Linux 2.6.7-2mdk.
  # rpm -qa | grep -i gtk+ | sort
  gtk+2.0-2.4.3-1mdk.i586.rpm
  gtk+mdk-0.1.6-14mdk.i586.rpm
  libgtk+-x11-2.0_0-2.4.3-1mdk.i586.rpm
  libgtk+1.2-1.2.10-38mdk.i586.rpm
  libgtk+1.2-devel-1.2.10-38mdk.i586.rpm
  libgtk+2.0_0-2.4.3-1mdk.i586.rpm
  libgtk+2.0_0-devel-2.4.3-1mdk.i586.rpm
  libgtk+mdk0.1_6-0.1.6-14mdk.i586.rpm
Hmmm.  "Compiled with GTK+ 2.4.2" vs "gtk+2.0-2.4.3-1mdk.i586.rpm".
Is this an issue?  Have I again shot myself in the foot by using
the Mandrake Cooker?

Google found me this page, indicating that compiling with "-O[23]"
would cause trouble, try rebuilding from source with "-O" only:
    http://www.ethereal.com/lists/ethereal-dev/200405/msg00539.html
I downloaded new source from www.ethereal.com and built it after
editing the "Configure" and make files accordingly, to find exactly
the same error behavior.

Any suggestions?

Bob



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA7F4NE0PBXmL+TdERApwTAKChSlzzPbbvmld3xti7yHzY+IVCewCguVKi
zxzDnBPrCBQcynWR79QVM7M=
=V32L
-----END PGP SIGNATURE-----