Ethereal-users: Re: [Ethereal-users] Bus error on solaris 5.7 (ethereal 0.8.13)

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

From: Guy Harris <gharris@xxxxxxxxxxxx>
Date: Mon, 30 Oct 2000 00:54:21 -0800
On Mon, Oct 30, 2000 at 09:23:15AM +0100, Kris Boulez wrote:
> This is a followup to an earlier posting, it can be found in the
> archives at
> http://www.ethereal.com/lists/ethereal-users/200010/msg00026.html
> 
> This to confirm that ethereal 0.8.13 also gives a bus error (and dumps
> core) on Solaris 5.7 with everything (GTK, lipcap,...) build from the
> latest sources. As described in this earlier mail tethereal works fine.
> 
> There was mention in this earlier mail that there was a bad patch for
> libICE (or whatever). Anyone who knows more about this ?

The earlier mail mentioned a message on a Helix GNOME mailing list; some
searching through the Web archives for that list (I'm not on any of
those lists - I'm not running Helix GNOME) for references to libICE
found

	http://lists.helixcode.com/archives/public/beta/2000-August/001222.html

If you need further help on that, I'd suggest asking the person who sent
that message to the Helix list (tony.taylor@xxxxxxxxxx).

However, as the stack trace from

	http://www.ethereal.com/lists/ethereal-users/200010/msg00024.html

doesn't show any libICE routines - it's just showing GTK+ routines -
that's probably not the problem.

It works fine on Solaris 2.6/SPARC, so it may be a problem somewhere in
later versions of Solaris, or it may be a compiler problem.

You may have to see if you can get any help from the
"gtk-list@xxxxxxxxx" mailing list; you will have to subscribe to it
first - see

	http://www.gtk.org/mailinglists.html

for information on that.

(I'll see if I have Solaris 7/SPARC available at work; I have Solaris
7/x86 at home, but that's probably not going to give any bus errors, as
bus errors usually mean a reference to a 2-byte or longer value not
aligned on its natural boundary, but those don't cause a problem on x86
unless the OS has set up the processor to do so, and I don't know of any
OSes that do.)