Date: Sat, 19 Jun 1999 16:03:24 +0200 (CEST) From: "Ronald 'Ko' Klop" <ronald@node11a94.a2000.nl> To: Doug White <dwhite@resnet.uoregon.edu> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: ghostscript 5.5 floating point exception Message-ID: <Pine.BSF.4.05.9906191558460.314-100000@dlanor.evertsen.nl> In-Reply-To: <Pine.BSF.4.10.9906181756420.34137-100000@resnet.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 18 Jun 1999, Doug White wrote: > On Thu, 17 Jun 1999, Ronald 'Ko' Klop wrote: > > > I compiled ghostscript 5.5 from the ports collection. When I run this > > program it immediately crashes with a floating point exception. I have a > > Cyrix 486DX and the kernel detects npx0 while booting. So, I have a FPU. > > > > Gs gets the signal in png_push_fill_buffer() which is an empty > > function in gdevpnm.c. I don't understand how a FPU exception can > > occure in an empty function. > > Did you use the port? > > This is a common Linux-ism. Linux masks all FPU exceptions by default, > where FreeBSD does not. The offending calls simply need to be bracketed > with fpgetmask()/fpsetmask() calls. > Yes, I did use the port. I discovered, that using optimalization (CFLAGS= -O ) didn't work very well. Compiling it without optimalization gives a good working binary. Thanks for the tip anyway. Greetings, Ronald. -- Ronald Klop http://node11a94.a2000.nl/~ronald/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9906191558460.314-100000>