From: Christian Thalinger <e9625286@student.tuwien.ac.at>
To: Zwane Mwaikambo <zwane@linux.realnet.co.sz>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
"Richard B. Johnson" <root@chaos.analogic.com>
Subject: Re: floating point exception
Date: 15 Jan 2002 19:19:13 +0100 [thread overview]
Message-ID: <1011118755.13266.0.camel@sector17.home.at> (raw)
In-Reply-To: <Pine.LNX.4.33.0201151633300.2080-100000@netfinity.realnet.co.sz>
In-Reply-To: <Pine.LNX.4.33.0201151633300.2080-100000@netfinity.realnet.co.sz>
On Tue, 2002-01-15 at 15:34, Zwane Mwaikambo wrote:
> On 14 Jan 2002, Christian Thalinger wrote:
>
> > It seems the floating point exception is only raised with a new data
> > package. Is there a simple way to raise such a exception?
>
> New data package? And does the same behaviour re-occur after the fpu
> exception? ie programs start segfaulting etc. Can you try doing a "dmesg"
> after the segfaults and fpu exception and see if there is anything in the
> kernel ring buffer too.
>
> Regards,
> Zwane Mwaikambo
>
There are .sah files, in which the data is stored to analyse. So i
deleted these files and the client downloads a new package -> new data
package.
Yes, it did happen that the segfault reoccured and there is nothing in
the dmesg. This was also my first thought, then checked
/var/log/messages with a tail and it stucked. No ctrl-c.
Tried this:
#define _GNU_SOURCE 1
#include <fenv.h>
main() {
double zero=0.0;
double one=1.0;
feenableexcept(FE_ALL_EXCEPT);
one /=zero;
}
...but nothing happens.
next prev parent reply other threads:[~2002-01-15 18:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 10:56 Zwane Mwaikambo
2002-01-14 21:26 ` Christian Thalinger
2002-01-15 14:34 ` Zwane Mwaikambo
2002-01-15 14:46 ` Richard B. Johnson
2002-01-15 18:19 ` Christian Thalinger [this message]
2002-01-15 18:31 ` Richard B. Johnson
2002-01-15 18:49 ` Christian Thalinger
2002-01-16 5:45 ` Zwane Mwaikambo
2002-01-16 11:55 ` Christian Thalinger
2002-01-16 14:32 ` Zwane Mwaikambo
2002-01-16 20:26 ` Christian Thalinger
2002-01-16 21:23 ` Richard B. Johnson
2002-01-16 21:59 ` Brian Gerst
2002-01-16 22:05 ` Richard B. Johnson
2002-01-16 22:12 ` Mark Zealey
2002-01-16 22:23 ` Richard B. Johnson
2002-01-16 23:35 ` Christian Thalinger
-- strict thread matches above, loose matches on Subject: below --
2002-12-27 14:18 Floating Point Exception Nandakumar NarayanaSwamy
2002-01-13 12:43 floating point exception Christian Thalinger
2002-01-15 23:28 ` Brian Gerst
2002-01-16 11:45 ` Christian Thalinger
2002-01-16 11:58 ` Dave Jones
2002-01-16 20:06 ` Christian Thalinger
2002-01-16 13:14 ` Bruce Harada
2002-01-17 19:26 ` bill davidsen
2002-01-16 13:52 ` Brian Gerst
2002-01-16 14:28 ` M. Edward (Ed) Borasky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1011118755.13266.0.camel@sector17.home.at \
--to=e9625286@student.tuwien.ac.at \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=zwane@linux.realnet.co.sz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®