From: Jim Blandy <jimb@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Satya <satya@ittc.ku.edu>, gdb@sources.redhat.com
Subject: Re: debugging gdb with itself
Date: Tue, 24 Sep 2002 20:16:00 -0000 [thread overview]
Message-ID: <vt24rceixgk.fsf@zenia.red-bean.com> (raw)
In-Reply-To: <20020924203628.GA7593@nevyn.them.org>
Daniel Jacobowitz <drow@mvista.com> writes:
> On Tue, Sep 24, 2002 at 03:33:09PM -0500, Satya wrote:
> >
> > Hi,
> > I am trying to debug gdb with gdb with itself. I copied gdb into gdb2 and
> > debugging gdb2 with gdb. When i am debugging a program with gdb2, if i
> > want to come back to the higher level gdb, how do i do that?
>
> Hit control-C?
The .gdbinit script that gets placed in the gdb build directory lets
you type `info' (with no arguments) to pop back out, and then
`continue' to go back in.
prev parent reply other threads:[~2002-09-25 3:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 21:20 breakpoint Vinayak P Risbud
2002-09-24 13:33 ` debugging gdb with itself Satya
2002-09-24 13:36 ` Daniel Jacobowitz
2002-09-24 20:16 ` Jim Blandy [this message]
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=vt24rceixgk.fsf@zenia.red-bean.com \
--to=jimb@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=satya@ittc.ku.edu \
/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