From:	noer AT cygnus DOT com (Geoffrey Noer)
Subject:	Debugging cygwin.dll with gdb
8 Jun 1997 00:31:30 -0700 :
Sender:	mail AT cygnus DOT com
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<199706080413.VAA14884.cygnus.gnu-win32@rtl.cygnus.com>
Original-To:	cgf AT bbc DOT com
Original-Cc:	gnu-win32 AT cygnus DOT com
In-Reply-To:	<EBB7qI.345@bbc.com> from "Chris Faylor" at Jun 5, 97 03:44:42 pm
X-Mailer:	ELM [version 2.4 PL23]
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

Chris Faylor wrote:
[...]
> I am at a loss, however, as to how to debug this.  I've built a cygwin.dll
> from scratch with Sergey's patches, but then, how do I debug it?  Attempting
> to invoke gdb remotely hangs due to the problem I mentioned above.
[...]

A future change that needs to be made is to always build cygwin.dll
and libcygwin.a as well as (new) cygwindebug.dll and libcygwindebug.a.
Everything other than gdb would get linked against cygwin.dll whereas
gdb would be linked against cygwindebug.dll.

So if you need to debug a non-functional cygwin.dll, you could use any
previously working gdb since it would depend on a working cygwin.dll.
Alternatively, we could somehow statically link the code inside the
cygwin.dll inside gdb.

-- 
Geoffrey Noer
noer AT cygnus DOT com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -