This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: 1.7.1: terminal not passing Ctrl-C to sub-sub cygwin processes
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 15 Jan 2010 18:22:13 -0500
- Subject: Re: 1.7.1: terminal not passing Ctrl-C to sub-sub cygwin processes
- References: <hiqoi4$7c5$1@ger.gmane.org>
- Reply-to: cygwin at cygwin dot com
On Fri, Jan 15, 2010 at 05:00:37PM -0500, Rolf Campbell wrote:
> From within cygwin python, if I call os.system running a cygwin
>sub-process, and I hit Ctrl-C while that cygwin sub-process is running,
>the Ctrl-C does nothing (absolutely nothing -- nothing is printed,
>nothing terminates, no sound is made -- it's as if I didn't press the
>key at all).
>
>I've attached a simple script which easily reproduces the situation.
>When I run the script as "./ctrlc.py 0", Ctrl-C kill the process, but
>when I run it with an argument of 1 or more, hitting Ctrl-C has no effect.
>
>I have not testing this with anything other than python, but I have a
>feeling that it's not python related.
It probably isn't. From the linux man page:
NAME
system - execute a shell command
SYNOPSIS
#include <stdlib.h>
int system(const char *command);
DESCRIPTION
system() executes a command specified in command by calling /bin/sh -c
command, and returns after the command has been completed. During
execution of the command, SIGCHLD will be blocked, and SIGINT and
SIGQUIT will be ignored.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple