Mail Archives: cygwin/2003/09/24/17:21:30
--=-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: <http://members.aardvark.net.au/lifeless/keys.txt>.
--=-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--
- Raw text -