Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Reply-To: Cygwin List <cygwin AT cygwin DOT com>
Message-Id: <6.0.1.1.0.20040109113950.037a3cd0@127.0.0.1>
Date: Fri, 09 Jan 2004 11:50:03 -0500
To: cygwin AT cygwin DOT com
From: Larry Hall <cygwin-lh AT cygwin DOT com>
Subject: Re: control-spacebar
In-Reply-To: <20040109053314.GA3696@redhat.com>
References: <20040108204601 DOT C1DDB3C063 AT juggler DOT cs DOT utah DOT edu> <Pine DOT GSO DOT 4 DOT 56 DOT 0401081550250 DOT 8635 AT slinky DOT cs DOT nyu DOT edu> <Pine DOT GSO DOT 4 DOT 56 DOT 0401081633300 DOT 18895 AT slinky DOT cs DOT nyu DOT edu> <20040108220309 DOT E7E393C063 AT juggler DOT cs DOT utah DOT edu> <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040108170956 DOT 04118050 AT 127 DOT 0 DOT 0 DOT 1> <Pine DOT GSO DOT 4 DOT 56 DOT 0401081721250 DOT 19598 AT slinky DOT cs DOT nyu DOT edu> <20040108223508 DOT EFF7B3C063 AT juggler DOT cs DOT utah DOT edu> <3FFE04E3 DOT DFC40A2A AT dessent DOT net> <20040109053314 DOT GA3696 AT redhat DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 12:33 AM 1/9/2004, Christopher Faylor you wrote:
>On Thu, Jan 08, 2004 at 05:33:23PM -0800, Brian Dessent wrote:
>>"H. James de St. Germain" wrote:
>>>at the time...  Its curious that it works in either place and even more
>>>curious that placing it after cygwin starts causes programs like rxvt
>>>to core dump.
>>
>>Why should that be curious?  As Chris pointed out it has to be set
>>before cygwin1.dll initializes.
>
>It certainly shouldn't SEGV if it is set in an rc file but it is curious
>why someone would comment on the curious nature of something that was
>already acknowledged by Larry as a potential bug.


Yeah, I know it's going out on a limb to suggest that a segv is a bug.
I'm a bit radical when it comes to things like that.  Any segv I tend 
to call "bugs", whether I find them curious or not.  I'm also of the 
notion that all "bugs" should segv.  That would make the job of finding 
and fixing "bugs" allot easier, right?  So when you write some code that 
will cause a "bug", please do so in such a way that it will always segv. 
This will streamline the bug reporting and resolution process immensely.

--
Larry
(Newly self-appointed Cygwin bug standard's officer) 


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