broken CTRL-BREAK handling

Troy Noble troy.noble@channelpoint.com
Tue Jul 17 13:06:00 GMT 2001


b20.1 handled it differently.  If I press the [X] or
CTRL-BREAK in a b20.1 window, JDK dutifully dumps the
stack trace.

Just one of several things that worked in b20.1 that are
broken in cygwin 1.x.

Troy

-----Original Message-----
From: Christopher Faylor [ mailto:cgf@redhat.com ]
Sent: Tuesday, July 17, 2001 1:37 PM
To: cygwin@cygwin.com
Subject: Re: broken CTRL-BREAK handling


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/

--
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/



More information about the Cygwin mailing list