From: paawan oza <paawan1982@yahoo.com>
To: gdb@sourceware.org
Subject: why SIGINT top stop the process, why was not SIGSTOP used ?
Date: Tue, 10 Feb 2009 16:35:00 -0000 [thread overview]
Message-ID: <911642.1896.qm@web36203.mail.mud.yahoo.com> (raw)
Hello,
I have been changing gdb.
as gdb uses ctrl+c (send SIGINT) to stop the process......
I am also doing the same.
but I have observed with gdb-6.7
that if process has blocked SIGINT, then actually gdb will not get SIGINT back.
I think this mechanism has been there for a long time.
my doubt is : why is this design of SIGINT?
why can not we use SIGSTOP ? because process cant block SIGSTOP.
though default gdb is configured to pass signal SIGSTOP (we can set it to 0)
but instead of SIGINT, cant we use SIGSTOP to stop the process ?
Regards,
..Paawan.
next reply other threads:[~2009-02-10 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 16:35 paawan oza [this message]
2009-02-10 16:42 ` Daniel Jacobowitz
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=911642.1896.qm@web36203.mail.mud.yahoo.com \
--to=paawan1982@yahoo.com \
--cc=gdb@sourceware.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