From: Jagadeesh Bhaskar P <jbhaskar@hclinsys.com>
To: Linux Newbie <linux-newbie@vger.kernel.org>
Subject: Query on SIGFPE handling
Date: Mon, 22 Nov 2004 11:56:12 +0530 [thread overview]
Message-ID: <1101104772.4527.7.camel@myLinux> (raw)
Hi,
I wrote a the small program, to c how signals can be caught by
customized routines.
/*********** start of code ********/
#include <stdio.h>
#include <signal.h>
void fe(void){
printf("floating pt exception:\n");
}
int main(void){
signal(SIGFPE, (void *)fe);
printf("%f\n", (1/0));
return 0;
}
/********** end of code *************/
It goes on catching the signal infinitely, and if i didnt do the
customization of that signal handling, it comes only once and then
exits.
What is the reason? Isnt it supposed to generate a signal once per
event?
Someone please do reply,
--
With regards,
Jagadeesh Bhaskar P
R&D Engineer
HCL Infosystems Ltd
Pondicherry
INDIA
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next reply other threads:[~2004-11-22 6:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 6:26 Jagadeesh Bhaskar P [this message]
2004-11-22 7:00 ` Query on SIGFPE handling Manish Regmi
2004-11-22 7:15 ` Jagadeesh Bhaskar P
2004-11-22 8:24 ` Jagadeesh Bhaskar P
[not found] ` <01ca01c4d071$5b35f080$121aa8c0@ascindia.com>
2004-11-22 9:05 ` Jagadeesh Bhaskar P
2004-11-22 9:19 ` Manish Regmi
2004-11-22 9:26 ` Jagadeesh Bhaskar P
2004-11-22 9:26 ` Manish Regmi
2004-11-22 11:15 ` joy merwin monteiro
[not found] ` <652016d3041122001540a047fd@mail.gmail.com>
[not found] ` <1101113860.5382.36.camel@myLinux>
2004-11-22 9:09 ` further query signal handling! Manish Regmi
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=1101104772.4527.7.camel@myLinux \
--to=jbhaskar@hclinsys.com \
--cc=linux-newbie@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.