1.7.1: terminal not passing Ctrl-C to sub-sub cygwin processes
Rolf Campbell
rcampbell-cygwin@dragonwaveinc.com
Sat Jan 16 09:17:00 GMT 2010
On 2010-01-15 18:22, Christopher Faylor wrote:
> 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).
[snip]
>
> 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
>
Thanks for setting me straight. When I change my script to use
os.popen, ^C gets propagated to sub-processes.
--
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
More information about the Cygwin
mailing list