X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Tue, 6 Apr 2010 10:11:11 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Cannot stop "cygcheck -c"
Message-ID: <20100406141111.GB16409@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <Pine DOT NEB DOT 4 DOT 64 DOT 1004051548230 DOT 12027 AT panix2 DOT panix DOT com>  <4BBA4E05 DOT 8030602 AT redhat DOT com>  <20100405213550 DOT GA11775 AT ednor DOT casa DOT cgf DOT cx>  <20100406082938 DOT GR18530 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100406082938.GR18530@calimero.vinschen.de>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Tue, Apr 06, 2010 at 10:29:38AM +0200, Corinna Vinschen wrote:
>On Apr  5 17:35, Christopher Faylor wrote:
>> On Mon, Apr 05, 2010 at 02:54:29PM -0600, Eric Blake wrote:
>> >On 04/05/2010 02:54 PM, Tim McDaniel wrote:
>> >> I'm running the latest setup.exe, cygwin libraries, and installed
>> >> packages.  I ran "cygcheck -c" (thanks to the list member who pointed
>> >> it out).  After a screen or two, I wanted to stop the output to scroll
>> >> back.  It doesn't seem to respond to control-C or control-Z.  Does
>> >> this happen to anyone else?
>> >
>> >Yes, this is an unfortunate side-effect of cygcheck being a native
>> >windows program rather than a cygwin app.  It doesn't know how to
>> >respond to cygwin signals.
>> 
>> That shouldn't matter.  If you're running it from bash then CTRL-C should
>> still terminate the process unless there's a bug.
>
>Curious side-point:  You can't even Ctrl-C cygcheck when running from
>a CMD shell.

On thinking about this more, I'll bet this is because cygcheck is a
pseudo-cygwin process which loads the cygwin DLL dynamically.  Probably
adding a CTRL-C handler would solve this problem.

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