Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<001301c07d3f$34d79850$0200a8c0@voyager>
From:	"Trevor Forbes" <trevorforbes AT ozemail DOT com DOT au>
To:	"Cygwin" <cygwin AT cygwin DOT com>
Subject:	Debugging cygwin1.dll
Date:	Sat, 13 Jan 2001 18:26:42 +0930
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400

I have tried to debug cygwin1.dll with limited success. I am able to trace
the source through the cygwin1.dll until "gdb itself" just stacks dumps with
an access violation which then just reloads gdb (error_start).

I have gdb and a debug cygwin1.dll in the same directory but not in my path.
I run GDB from cmd.exe and then load the program under test and set the
breakpoints as usual.

Is there a more reliable method of debugging the cygwin1.dll?

Would I be better to remotely debug cygwin from my Linux box? Is there any
gdb stub to achieve this?

Any pointers would be appreciated.

Regards Trevor


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -