Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Tue, 17 Jul 2001 16:28:46 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: broken CTRL-BREAK handling Message-ID: <20010717162846.A11316@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <8F23E55D511AD5119A6800D0B76FDDE1CA2EF1 AT cpex3 DOT channelpoint DOT com> <20010717161453 DOT A11212 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010717161453.A11212@redhat.com>; from cgf@redhat.com on Tue, Jul 17, 2001 at 04:14:53PM -0400 On Tue, Jul 17, 2001 at 04:14:53PM -0400, Christopher Faylor wrote: >On Tue, Jul 17, 2001 at 02:06:21PM -0600, Troy Noble wrote: >>b20.1 handled it differently. If I press the [X] or >>CTRL-BREAK in a b20.1 window, JDK dutifully dumps the >>stack trace. > >Hmm. I'll have to investigate this next week. I can't easily retrieve >the B20 sources right now. Ok. I lied. I can check this. I reverted some sources to around the B20 time frame. AFAICT, my original assertion is true. B20 should have treated CTRL-BREAK as equivalent to CTRL-C. If it didn't then it sure appears to be a bug. I can't figure out how CTRL-C could work if CTRL-BREAK wasn't also working the same way. 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/