Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <71A0F7B0F1F4F94F85F3D64C4BD0CCFE02BF255E@bmkc1svmail01.am.mfg>
From: "Parker, Ron" <rdparker AT butlermfg DOT com>
To: cygwin AT cygwin DOT com
Subject: Debugging cygwin1.dll startup
Date: Wed, 24 Sep 2003 12:40:46 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"

I have made some local changes to the source for cygwin1.dll and would like
to debug it, as the first Cygwin process, bash, begins.  I know about using
a gdb-startup.cmd setup for JIT debugging applications, but this does not
seem to work for debugging Cygwin prior to reaching a bash prompt.  Is the
'dll cygwin1' GDB mechanism the only way to do what I need?

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/