Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Dave Korn" <dk AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: snapshot now == 1.5.7 soon, please try
Date: Wed, 21 Jan 2004 18:42:37 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <Pine.GSO.4.58.0401211223310.17483@eos>
Message-ID: <NUTMEGf6FquXctGbiij0000017c@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 21 Jan 2004 18:42:37.0699 (UTC) FILETIME=[57863530:01C3E04E]


> -----Original Message-----
> From: cygwin-owner On Behalf Of Brian Ford
> 
> On Wed, 21 Jan 2004, Christopher Faylor wrote:
> 
> > Ok.  So, I took ten minutes and debugged the problem myself 
> and I'll 
> > check in a fix.

  Thanks cgf, I'll give it some testing as well.

> Thank you.
> 
> That is why I asked.  You know your way around, so it takes 
> you *much* less time.
> 
> I really have been looking at it all this time, and I'm still 
> lost in a few places.  It is not laziness or skill 
> necessarily, just the learning curve.

  I'd also like to express that it's not lack of *willing* that's kept me
from trying to debug this in the .dll, just the way that over the past week
the cvs HEAD was b0rked for a while, giving me completely non-functional
dlls, and then when that got better "make check" started playing up on me,
for no perceivable reason.

  If I can't even get the cvs code to build and pass make check, despite
doing all the correct things and having several years of experience with
gnu-style configure and make, then I can't even get off square one when it
comes to debugging.  Sorry.

  In the end I was obliged to bypass cygwin and write a win32 serial i/o
layer for my program, because I needed to make progress in the job which I'm
actually getting paid to do, and felt bad about ploughing too many of my
paid hours into a diversion-from-the-main-point.

  None of this, btw, should be taken as any kind of personal criticism,
finger-pointing, or even dissatisfied complaining about the cygwin project
and everyone working for it: my appreciation for your efforts is entirely
undiminished by the occasional problem.  Hell, I've been working in software
long enough to know that things do just go wrong and sometimes there's no
quick fix :-/



    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


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