From: Tom Emerson <tremerson@gmail.com>
To: Smith John <baseboy126@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: How to debug gdb using gdb ?
Date: Tue, 07 Aug 2012 14:21:00 -0000 [thread overview]
Message-ID: <CAOL6EhujAGv-g1Y84F36g_BgMKu4DxpGaUE5duw51OsggagfvA@mail.gmail.com> (raw)
In-Reply-To: <CA+zazRVEWjmAhfoXO4vG6rX5Eiry_Un6AF26pE8D+jbZei5iLg@mail.gmail.com>
http://sourceware.org/gdb/current/onlinedocs/gdbint/Debugging-GDB.html#Debugging-GDB
On Tue, Aug 7, 2012 at 10:18 AM, Smith John <baseboy126@gmail.com> wrote:
> hi,guys:
>
> I am researching gdb source code , and I want to debug it
> using its executable file .
> but how can I send command to the debugged gdb procedure
> which is children process ,
>
> as the gdb which is parent process will deal with every command
> inputed from the command line ,so I get no way to communicate with
>
> that debugged gdb procedure.
>
>
>
> any advice?
>
>
> thanks!
--
Tom Emerson
tremerson@gmail.com
http://www.dreamersrealm.net/tree
next prev parent reply other threads:[~2012-08-07 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 14:18 Smith John
2012-08-07 14:21 ` Tom Emerson [this message]
2012-08-07 14:22 ` Jan Kratochvil
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=CAOL6EhujAGv-g1Y84F36g_BgMKu4DxpGaUE5duw51OsggagfvA@mail.gmail.com \
--to=tremerson@gmail.com \
--cc=baseboy126@gmail.com \
--cc=gdb@sourceware.org \
/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).