From owner-freebsd-stable Thu Oct 25 9:46: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id 321BD37B407 for ; Thu, 25 Oct 2001 09:45:58 -0700 (PDT) Received: (from olli@localhost) by lurza.secnetix.de (8.11.6/8.11.6) id f9PGjuD10016; Thu, 25 Oct 2001 18:45:56 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Date: Thu, 25 Oct 2001 18:45:56 +0200 (CEST) Message-Id: <200110251645.f9PGjuD10016@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG Reply-To: freebsd-stable@FreeBSD.ORG Subject: Re: SIGPFE problems on Athlon processors running 4.3-STABLE In-Reply-To: <3BD75C6C.8070201@ludd.luth.se> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.4-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Joachim Strömbergson wrote: > Yes, SIGPFE are floating point exceptions. See man signal. The question is if > anybody have any clue why this happens on the Athlon for GPG. And how to fix. Doesn't happen on my Athlon. Did you compile the program with any unsupported optimizations, such as -O2 or higher, do you have a CPUTYPE setting in your make.conf, or anything else that is non-standard? If so, try compiling it with just -O, no CPUTYPE or anything. Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message