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:14:53 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: broken CTRL-BREAK handling Message-ID: <20010717161453.A11212@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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <8F23E55D511AD5119A6800D0B76FDDE1CA2EF1@cpex3.channelpoint.com>; from troy.noble@channelpoint.com on Tue, Jul 17, 2001 at 02:06:21PM -0600 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. >Just one of several things that worked in b20.1 that are >broken in cygwin 1.x. I think I recall that back in B20.1 days, people routinely provided details rather than make vague assertions, too. Ah, those were the days. Everything was so very much better. 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/