Date: Mon, 8 Dec 97 14:24:56 EST From: luoqi@watermarkgroup.com (Luoqi Chen) To: jfieber@indiana.edu Cc: current@freebsd.org Subject: Re: Oddity with netscape and current Message-ID: <9712081924.AA12202@watermarkgroup.com>
next in thread | raw e-mail | index | archive | help
> For the record, the problem which this solves/works-around exists > in FreeBSD-2.2.5/XFree86-3.3.1 as well as (I gather) current (and > what version of X?). I'm using a 16 bit display and have not > tried it on 8 or 24. The reports on what works with what > combinations of FreeBSD, Netscape, and X11 have been rather > inconsistent--some curious methods of suppressing the symptoms > have been discovered but does anyone have a clue about the > problem? This has something to do with floating point exceptions. Netscape uses the fbsd default exception mask (precision/underflow/denomrmals), and *ignores* SIGFPE signal, which means when an unmasked exception arises, the FPU register stack will be completely messed up, and sometime this results in an infinite loop. To fix this problem, Netscape should either: 1. trap SIGFPE signals and handle the exceptions correctly, or 2. ignore SIGFPE, but use fpsetmask to mask ALL fp exceptions. Before Netscape fixes this problem, all we can do is to try to keep these unwanted exceptions from happening. Apparently, Netscape goes into an infinite loop when it does some CMS color lookup during startup. That's why I proposed to disable CMS by setting CMSDB to null. -lq > > -john > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9712081924.AA12202>