This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
why SIGINT top stop the process, why was not SIGSTOP used ?
- From: paawan oza <paawan1982 at yahoo dot com>
- To: gdb at sourceware dot org
- Date: Tue, 10 Feb 2009 08:34:54 -0800 (PST)
- Subject: why SIGINT top stop the process, why was not SIGSTOP used ?
- Reply-to: paawan1982 at yahoo dot com
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.