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: Thu, 14 Dec 2000 21:42:13 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: Anyone having problems with the latest winsup/cygwin1.dll?
Message-ID: <20001214214213.B22185@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <20001214183957 DOT B20516 AT redhat DOT com> <FMEOJCMLNIMPBKAPFPIHGEKFCFAA DOT tailbert AT yahoo DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <FMEOJCMLNIMPBKAPFPIHGEKFCFAA.tailbert@yahoo.com>; from tailbert@yahoo.com on Thu, Dec 14, 2000 at 08:17:30PM -0500

Be creative.  If Cygwin 1.1.6 is really not working for you (and this
would be the first I've heard of the problem) drop back to 1.1.4 and
use that with gdb.

Also, build your cygwin with --enable-debugging.

FWIW, this has been discussed here before.  Probably just searching for
'gdb' in the cygwin-developers archives should provide some clues.

cgf

On Thu, Dec 14, 2000 at 08:17:30PM -0500, edward wrote:
>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...