Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 9 Jan 2004 13:01:17 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: control-spacebar Message-ID: <20040109180117.GA18495@redhat.com> Mail-Followup-To: cygwin@cygwin.com References: <20040108204601.C1DDB3C063@juggler.cs.utah.edu> <20040108220309.E7E393C063@juggler.cs.utah.edu> <6.0.1.1.0.20040108170956.04118050@127.0.0.1> <20040108223508.EFF7B3C063@juggler.cs.utah.edu> <3FFE04E3.DFC40A2A@dessent.net> <20040109053314.GA3696@redhat.com> <6.0.1.1.0.20040109113950.037a3cd0@127.0.0.1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.0.1.1.0.20040109113950.037a3cd0@127.0.0.1> User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Reply-To: cygwin@cygwin.com On Fri, Jan 09, 2004 at 11:50:03AM -0500, Larry Hall wrote: >So when you write some code that will cause a "bug", please do so in >such a way that it will always segv. As it turns out, the problems that people are having with Windows ME in recent cygwin snapshots are really SEGV problems, so I've been apparently inadvertantly following this maxim. Now, if only I could get Windows to tell me exactly where the bug is occurring that would be wonderful. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/