Re: CTRL+C problem

["Robert Collins" <robert dot collins at itdomain dot com dot au>]

----- Original Message -----
From: "Alan Hourihane" <alanh@fairlite.demon.co.uk>
To: <cygwin-xfree@cygwin.com>
Sent: Thursday, June 07, 2001 7:55 PM
Subject: CTRL+C problem


> Has anyone seen this problem with hitting CTRL+C.....

I had some nasty problems with signals in 1.3.2 that aren't present on
my CVS based custom cygwin1.dll. (I never reported because by the time I
built a custom dll to investigate, they were apparently fixed in CVS :].

> launch a cygwin shell on your windows box.
>
> launch an xterm in the background.
>
> start a compile off (or something that takes time) in the xterm.
>
> start a compile off (or something that takes time) in the cygwin
shell.
>
> now hit CTRL+C in the cygwin shell.
>
> It ends up sending a signal to both xterm and the cygwin shell
stopping both
> compiles.

That's weird. Info gathering time:
I presume you started X after the xygwin shell, or before? Are you using
rxvt-win32 for the cygwin shell, or cmd.exe? What .dll version are you
running?

I'd suggest building from CVS and seeing if that helps.

Rob

> Anyone seen this ? It may be a problem with cygwin's signal handling
as the
> xterm process has been spawned in the background.
>
> I'm using NT 4.0 (SP6) with XFree86 4.1.0
>
> Alan.
>