Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Wed, 5 Sep 2001 18:21:14 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: jik, cwilson, earnie -- show stoppers
Message-ID: <20010905182114.D4391@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <20010905165512 DOT A3778 AT redhat DOT com> <20010905165709 DOT A3907 AT redhat DOT com> <3B96991D DOT 6060107 AT ece DOT gatech DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3B96991D.6060107@ece.gatech.edu>
User-Agent: Mutt/1.3.21i

On Wed, Sep 05, 2001 at 05:29:01PM -0400, Charles Wilson wrote:
>Now, fortunately for all of us, Egor (somehow) seems to have reproduced 
>"my" problem on his machine, and supplied a patch that seems to fix it. 
> On his machine.  If the bug he is seeing is the same as the one I used 
>to see, but don't see any longer.  I dunno if Egor's patch fixes *my* 
>bug on *my* machine, since my machine magically fixed itself.  Without 
>changing anything.
>
>Bleah.  (I'm a bit frustrated.  Can you tell?)

Yes, I can.  It sounds similar to how I feel when people report problems
that I can't reproduce.  But, I can sympathize even more strongly than
that.

FWIW, I spent a good amount of time a couple of weeks ago trying to
track down a very strange rsh memory corruption problem.  The problem
went away when run under strace, of course, and it usually went away
when running under the debugger.

Eventually, it just went away completely, just like your problem.  It
was quite frustrating.  I had a serious bug and then I didn't.  The
version of the DLL that manifested the error just started working and
I could never get it to fail again.

So, I know exactly how you feel.

cgf