kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: kernelmail.jms@gmail.com (julie Sullivan)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Enabling Signals in kernel
Date: Wed, 13 Apr 2011 20:30:10 +0100	[thread overview]
Message-ID: <BANLkTi=Zaoy9LbR_VKifoSjmJ7wYxPQ5OA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=ofpt1TY5LH35kEAfTt9tBfUU5yA@mail.gmail.com>

Hi Vijay

>> Putting this piece of code into a script doesn't catch the signal
>> SIGINT (ctrl+c). To understand if it was a problem with the shell, i
>> wrote a C code to register my own signal handler for SIGINT signal.

Incidentally there is a bug with Bash where ctrl+c isn't caught, see
this discussion on linux-kernel from February:

https://lkml.org/lkml/2011/2/5/191

I doubt if this is your problem though, for as you can see from the
discussion ctrl+c is only sporadically dropped in the shell, usually
it's caught OK.
Cheers
Julie

  reply	other threads:[~2011-04-13 19:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12 16:06 Enabling Signals in kernel Vijay Ram Chitrapu
2011-04-13  1:01 ` Haojian Zhuang
2011-04-13 19:30   ` julie Sullivan [this message]
2011-04-13 17:20 ` Missing 1GB RAM, where is it? Andrzej Kardas
2011-04-14  2:42   ` Mulyadi Santosa
2011-04-14 11:27     ` andrzej-kardas
2011-04-14 12:17       ` Mulyadi Santosa
2011-04-14 15:23         ` Andrzej Kardas
2011-04-16  6:07           ` Mulyadi Santosa
2011-04-14 15:09   ` Adrian Cornish
2011-04-14 15:43     ` Andrzej Kardas
2011-04-14 16:12       ` Haojian Zhuang
2011-04-15  0:45         ` Haojian Zhuang
     [not found]       ` <BANLkTik7g8vEf6X+suzwbXD1b4ow1__2xQ@mail.gmail.com>
2011-04-17  7:58         ` Missing 1GB RAM, where is it? - SUMMARY Andrzej Kardas
2011-04-17 15:31           ` julie Sullivan
2011-04-18 10:17             ` andrzej-kardas

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='BANLkTi=Zaoy9LbR_VKifoSjmJ7wYxPQ5OA@mail.gmail.com' \
    --to=kernelmail.jms@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).