Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Tue, 17 Jul 2001 15:36:54 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: broken CTRL-BREAK handling Message-ID: <20010717153654.B10822@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <8F23E55D511AD5119A6800D0B76FDDE1CA2EEE@cpex3.channelpoint.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <8F23E55D511AD5119A6800D0B76FDDE1CA2EEE@cpex3.channelpoint.com>; from troy.noble@channelpoint.com on Tue, Jul 17, 2001 at 01:00:25PM -0600 On Tue, Jul 17, 2001 at 01:00:25PM -0600, Troy Noble wrote: >In exceptions.cc:ctrl_c_handler > >I think the following code should be added: > > /* Return FALSE to allow other control handlers to handle CTRL-BREAK */ > if (type == CTRL_BREAK_EVENT) > return FALSE; > >before the section of code that checks the pids, sids, pgids etc. and >eventually culminates in a > > kill (-myself->pid, SIGINT); > >Without this code, the current behavior in cygwin 1.3.2 is to send >SIGINT to the process group whether you press CTRL-C or >CTRL-BREAK. Cygwin has considered CTRL-BREAK to be the same thing as CTRL-C for about five years or so. The fact that this inconveniences JDK is regrettable but I'm not going to change well established behavior just to accomodate some non-cygwin program. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/