Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Tue, 6 Aug 2002 01:34:25 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: cygthread + rxvt Message-ID: <20020806053425.GA14302@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <001e01c23cb5$403b4b10$6132bc3e AT BABEL> <20020805201505 DOT GA9710 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020805201505.GA9710@redhat.com> User-Agent: Mutt/1.3.23.1i On Mon, Aug 05, 2002 at 04:15:05PM -0400, Christopher Faylor wrote: >On Mon, Aug 05, 2002 at 08:21:07PM +0100, Conrad Scott wrote: >>Chris, >> >>I've picked up your latest cygthread.cc patch from a couple of >>hours back and I'm not getting far now. The most obvious problem >>I'm having is rxvt spinning when launched via: >> >>c:\cygwin\usr\X11R6\bin\run.exe rxvt -ls -e bash --login -i >> >>I'm also getting core dumps elsewhere, which I'll go check in a >>moment. If you need anymore information, give me a shout. All >>this is with a clean copy of the latest HEAD CVS compiled w/ >>debugging enabled. > >Hmm. I could have SWORN that I specifically tested rxvt before checking >in my changes but apparently I didn't because it is definitely not work. > >Sorry about that. I'll take a look. Yep. That was an interesting race. Like most races, it was really obvious once I found it. It seems to work ok now but I haven't tested it rigorously. I was lulled into a false sense of security before when I really *had* tested rxvt. I just didn't try it enough times to notice that it failed 50% of the time at least. cgf