Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <004f01bfbb08$e43e3dc0$0100000a@TIMYX18EWDT6RQ>
From: "Tim Prince" <tprince AT computer DOT org>
To: "Andrew Begel" <abegel AT cs DOT berkeley DOT edu>, <cygwin AT sourceware DOT cygnus DOT com>
References: <A629197179C1D211A86D00A0C981C254143D2D AT mmnt DOT Millennium DOT Berkeley DOT EDU>
Subject: Re: GDB hangs on Win2K
Date: Wed, 10 May 2000 20:15:57 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.5600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.5600

I'm trying to find out where cc1.exe is hanging up when
attempting to build snapshots.  All I know so far is that it
completes certain compilations with -O0 which it doesn't
with -O.  Thought gdb would be the route to finding out more.
No such luck.  I have installed cygwin since the mail about a
fix for this, but don't remember if we were told to do something
special.

----- Original Message -----
From: "Andrew Begel" <abegel AT cs DOT berkeley DOT edu>
To: <cygwin AT sourceware DOT cygnus DOT com>
Sent: Wednesday, May 10, 2000 7:38 PM
Subject: GDB hangs on Win2K


> I'm trying to use the Cygwin 1.1.0 version of GDB on my Win2K
box to debug
> an application I compiled with gcc. I load up gdb with the
debug version of
> my app, and hit run (well, gdb -nw). It says that it loads all
the DLLs my
> app is dependent on, but then hangs. I have to use the task
manager to quit
> my bash shell that started it. (Same thing happens on the
graphical version
> of gdb).
>
> The same app can be debugged perfectly on a WinNT box. (just
copied the
> binary over).
>
> Is there some easy way to enable/fix gdb debugging on Win2K?
>
> I did check it out a bit with the VC++ debugger (can't use gdb
to attach to
> processes on windows) and found that GDB was in an infinite
loop between
> cygwin1.dll and kernel32.dll. I don't yet have symbols for
kernel32.dll, and
> well, it appears that gcc symbols (even with -gcoff) aren't
compatible with
> Windows debuggers (which claim to use an extension of COFF),
so all I could
> tell was that it was in an infinite loop, and not what
functions it is
> running.
>
> Andrew
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com