From: Manish Regmi <regmi.manish@gmail.com>
To: Jagadeesh Bhaskar P <jbhaskar@hclinsys.com>
Cc: linux-newbie@vger.kernel.org, yogeshb@ascindia.com
Subject: Re: Query on SIGFPE handling
Date: Mon, 22 Nov 2004 15:11:10 +0545 [thread overview]
Message-ID: <652016d3041122012643ea7ffe@mail.gmail.com> (raw)
In-Reply-To: <1101114324.5382.42.camel@myLinux>
On Mon, 22 Nov 2004 14:35:24 +0530, Jagadeesh Bhaskar P
<jbhaskar@hclinsys.com> wrote:
> On Mon, 2004-11-22 at 14:27, Yogesh Bute wrote:
> > hi,
> > u need to inform the shell that the signal is handled - so u need to
> > SIG_IGN the singal ie. signal (signum, SIG_IGN) once u have done with
> > handling the signal
> > or u could send SIG_DFL, so that default singal handler will handle the
> > signal, after your specific signal handler code.
Doing that will probably put you in infinite loop.
Infact, the is no way to go further unless you resolve the cause of
the exception.
For playing with Signals,
you can generate SIGUSR1 kill(pid, SIGUSR1) and catch.
--
Manish Regmi
-
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 prev parent reply other threads:[~2004-11-22 9:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 6:26 Query on SIGFPE handling Jagadeesh Bhaskar P
2004-11-22 7:00 ` 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 [this message]
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=652016d3041122012643ea7ffe@mail.gmail.com \
--to=regmi.manish@gmail.com \
--cc=jbhaskar@hclinsys.com \
--cc=linux-newbie@vger.kernel.org \
--cc=yogeshb@ascindia.com \
/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