This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: why SIGINT top stop the process, why was not SIGSTOP used ?
- From: Daniel Jacobowitz <drow at false dot org>
- To: paawan oza <paawan1982 at yahoo dot com>
- Cc: gdb at sourceware dot org
- Date: Tue, 10 Feb 2009 11:41:53 -0500
- Subject: Re: why SIGINT top stop the process, why was not SIGSTOP used ?
- References: <911642.1896.qm@web36203.mail.mud.yahoo.com>
On Tue, Feb 10, 2009 at 08:34:54AM -0800, paawan oza wrote:
> Hello,
>
> I have been changing gdb.
> as gdb uses ctrl+c (send SIGINT) to stop the process......
> I am also doing the same.
GDB is not sending the SIGINT. On most systems, GDB puts the process
in the foreground terminal process group, and the operating system
is responsible for sending the SIGINT.
Using SIGSTOP has some other weird effects on job control, especially
in threaded applications.
--
Daniel Jacobowitz
CodeSourcery