RE: Question on SIGFPE
From: Sreeram Kumar Ravinoothala
Date: Thu Oct 30 2003 - 07:06:29 EST
Hi,
I tried this. It says that the address is 0. And also I saw that
it doesn't fall into any of the si_codes of SIGFPE.
Regards
Sreeram
---Never doubt that a small group of thoughtful, committed people can
change the world. Indeed, it is the only thing that ever has. -- Copied
from a mail
-----Original Message-----
From: Magnus Naeslund(t) [mailto:mag@xxxxxxxx]
Sent: Thursday, October 30, 2003 3:53 PM
To: Sreeram Kumar Ravinoothala
Cc: linux-kernel@xxxxxxxxxxxxxxx
Subject: Re: Question on SIGFPE
Sreeram Kumar Ravinoothala wrote:
> Hi,
> We get this problem when we run it on disk on chip where linux
> 2.4.5 is used.
>
> Thanks and Regards
> Sreeram
Since I don't know what your app is doing, it's kind of hard to know
whats causing the problem. I still would guess on a divide by zero,
maybe because of some timing issue.
Use sigaction(2) to trap the signal, and then look at the
siginfo_t->si_addr to find out where it happens.
Or better yet, just run the program through gdb, it will catch the
thing...
Magnus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/