From: Daniel Jacobowitz <drow@false.org>
To: paawan oza <paawan1982@yahoo.com>
Cc: gdb@sourceware.org
Subject: Re: why SIGINT top stop the process, why was not SIGSTOP used ?
Date: Tue, 10 Feb 2009 16:42:00 -0000 [thread overview]
Message-ID: <20090210164153.GA1099@caradoc.them.org> (raw)
In-Reply-To: <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
prev parent reply other threads:[~2009-02-10 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 16:35 paawan oza
2009-02-10 16:42 ` Daniel Jacobowitz [this message]
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=20090210164153.GA1099@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=paawan1982@yahoo.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