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
X-Authentication-Warning: sequoia.cs.berkeley.edu: maratb set sender to maratb AT CS DOT Berkeley DOT EDU using -f
To: Andrew Begel <abegel AT CS DOT Berkeley DOT EDU>
Cc: "'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re: GDB hangs on Win2K
References: <A629197179C1D211A86D00A0C981C254143D2D AT mmnt DOT Millennium DOT Berkeley DOT EDU>
From: Marat Boshernitsan <maratb AT CS DOT Berkeley DOT EDU>
Date: 10 May 2000 22:59:34 -0700
In-Reply-To: Andrew Begel's message of "Wed, 10 May 2000 19:38:58 -0700"
Message-ID: <tfvya5hvd89.fsf@sequoia.cs.berkeley.edu>
Lines: 38
User-Agent: Gnus/5.0803 (Gnus v5.8.3) XEmacs/21.1 (Biscayne)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii


This is the message Chris was refering to:

http://sourceware.cygnus.com/ml/cygwin/2000-04/msg00420.html

Just get his version of gdb.

Marat.


Andrew Begel <abegel AT CS DOT Berkeley DOT EDU> writes:

> 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