Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com From: "edward" To: Subject: RE: Anyone having problems with the latest winsup/cygwin1.dll? Date: Thu, 14 Dec 2000 20:17:30 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <20001214183957.B20516@redhat.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Apparently-From: Swiftnsavv AT aol DOT com That brings up another question... How does one start gdb when I can't start a shell using cygwin1.dll? edward -----Original Message----- From: cygwin-developers-owner AT sources DOT redhat DOT com [mailto:cygwin-developers-owner AT sources DOT redhat DOT com]On Behalf Of Christopher Faylor Sent: Thursday, December 14, 2000 6:40 PM To: Cygwin Developers List Subject: Re: Anyone having problems with the latest winsup/cygwin1.dll? Since this happens very early in the initialization phase and no other threads are running, it should be pretty easy to figure out what's happening. Single step until you see it happen... cgf