Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Subject: Re: Debugging cygwin1.dll startup From: Robert Collins To: "Parker, Ron" Cc: cygwin AT cygwin DOT com In-Reply-To: <71A0F7B0F1F4F94F85F3D64C4BD0CCFE02BF255E@bmkc1svmail01.am.mfg> References: <71A0F7B0F1F4F94F85F3D64C4BD0CCFE02BF255E AT bmkc1svmail01 DOT am DOT mfg> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-54GDjIhZaTUkqKfSk1LO" Message-Id: <1064438461.939.46.camel@localhost> Mime-Version: 1.0 Date: Thu, 25 Sep 2003 07:21:01 +1000 --=-54GDjIhZaTUkqKfSk1LO Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2003-09-25 at 03:40, Parker, Ron wrote: > I have made some local changes to the source for cygwin1.dll and would li= ke > to debug it, as the first Cygwin process, bash, begins. I know about usi= ng > 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 th= e > 'dll cygwin1' GDB mechanism the only way to do what I need? Don't install the new cygwin1.dll if you've broken startup ;). So the answer is, I think, yes. What I usually do when fiddling cygwin1.dll startup stuff (like when I was prodding gprof) is to have gdb have it's own copy of cygwin1.dll, isolated. Then gdb runs fine and one can dig into the new process happily. Rob --=20 GPG key available at: . --=-54GDjIhZaTUkqKfSk1LO Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQA/cgq9I5+kQ8LJcoIRAg1iAJ9iiB+uRjw5vlL7ryBsLf/EUf3thgCeJYji ODsSLKmZv8iYZx3Tahj11/Y= =SK2d -----END PGP SIGNATURE----- --=-54GDjIhZaTUkqKfSk1LO--