From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christopher Faylor <cgf@redhat.com>
To: GDB <gdb@sources.redhat.com>
Subject: Re: How do you use GDB to debug GDB
Date: Wed, 21 Mar 2001 15:59:00 -0000
Message-id: <20010319195040.D29979@redhat.com>
References: <3AB66BE3.D45096D0@home.com> <3AB6724D.19D8A981@cygnus.com> <o5r8zt1irn.fsf@toenail.toronto.redhat.com>
X-SW-Source: 2001-03/msg00179.html

On Mon, Mar 19, 2001 at 05:44:12PM -0500, Frank Ch. Eigler wrote:
>Fernando Nasser <fnasser@cygnus.com> writes:
>: [...]
>: Start your "top" gdb in a separate shell.  Use the command attach passing the Windows 
>: PID (as opposed to the Unix PID) of the other GDB.
>: [...]
>
>By the way, why does cygwin gdb use Windows PIDs only instead of
>cygwin PIDs, or some fall-back defaulting from one to the other?

GDB uses Windows pids because it can debug more than just cygwin
applications.  In older DLLs it was possible to have the same number
indicate both a Windows PID and a Cygwin PID, so there was ambiguity.
You don't want to have a mechanism which disallows the ability to
debug a program or ends up debugging the wrong program.

In current net releases of Cygwin it is (or should be) impossible
to have the cygwin pid == the windows pid except for when they
are the same process.

So, I guess you could have a fallback mechanism if somebody wanted
to implement it.

cgf