From: Fernando Nasser <fnasser@cygnus.com>
To: Stephen Smith <ischis2@home.com>
Cc: GDB <gdb@sourceware.cygnus.com>
Subject: Re: How do you use GDB to debug GDB
Date: Wed, 21 Mar 2001 15:59:00 -0000 [thread overview]
Message-ID: <3AB6724D.19D8A981@cygnus.com> (raw)
In-Reply-To: <3AB66BE3.D45096D0@home.com>
Stephen Smith wrote:
>
> I have a gdb debugger configured to for a remote target (host i686-pc-cygwin target=powerpc-motorola-elf). normally I
> run gdb as:
>
> powerpc-motorola-elf-gdb --command=C:/rti/bin/rtidbug.ini C:/examples/dll/main.exe
>
> Now I want to run the gdb against the above process. Since I am running this in a Windows NT command shell I can't use
> gdb /usr/local/bin/powerpc-motorola-elf-gdb some_process_id
>
> Can someone help
>
Use the "ps -l" command. It will give you the Windows PID in addition to the Unix (Cygwin) one.
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.
You are now debugging your powerpc-motorola-elf-gdb
Good luck.
--
Fernando Nasser
Red Hat - Toronto E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
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 ` J.T. Conklin
2001-03-21 15:59 ` Fernando Nasser [this message]
2001-03-21 15:59 ` Frank Ch. Eigler
2001-03-21 15:59 ` Christopher Faylor
-- strict thread matches above, loose matches on Subject: below --
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
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
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=3AB6724D.19D8A981@cygnus.com \
--to=fnasser@cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=ischis2@home.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).