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 [thread overview]
Message-ID: <20010319195040.D29979@redhat.com> (raw)
In-Reply-To: <o5r8zt1irn.fsf@toenail.toronto.redhat.com>
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
next prev parent reply other threads:[~2001-03-21 15:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 15:59 Stephen Smith
2001-03-21 15:59 ` Fernando Nasser
2001-03-21 15:59 ` Frank Ch. Eigler
2001-03-21 15:59 ` Christopher Faylor [this message]
2001-03-21 15:59 ` J.T. Conklin
-- strict thread matches above, loose matches on Subject: below --
2001-03-21 15:59 Michael Elizabeth Chastain
2001-03-21 15:59 ` Stephen Smith
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 ` Kevin Buettner
2001-03-21 15:59 ` Andrew Cagney
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 ` Stephen Smith
2001-03-21 15:59 Michael Elizabeth Chastain
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 Michael Elizabeth Chastain
2001-03-21 15:59 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010319195040.D29979@redhat.com \
--to=cgf@redhat.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).