From: Tim Combs <tcombs@urbana.css.mot.com>
To: James Sampson <i_am_triumph@ofir.dk>
Cc: GDB Archive <gdb@sources.redhat.com>
Subject: Re: Debugging GDB with GDB
Date: Thu, 14 Nov 2002 06:58:00 -0000 [thread overview]
Message-ID: <20021114085605.A6694@urbana.css.mot.com> (raw)
In-Reply-To: <20021114143821.F19325A9BB@postfix3.ofir.com>; from i_am_triumph@ofir.dk on Thu, Nov 14, 2002 at 03:13:07PM +0100
The .gdbinit file uses "set prompt (top-gdb)" so you can differentiate
between which gdb is running. This works best on
the command line as you can readily see which gdb you are in. Things
work the same as when you are debugging a program. When you want to
stop use ctrl-c and you will see the top-level prompt and you can step
through gdb source. When using the command line, I've always found it
helpful to open the source file I'm debugging to follow along.
Hope this helps
Tim
On Thu, Nov 14, 2002 at 03:13:07PM +0100, James Sampson wrote:
> Hello
>
> GDB doesn't recognize a COFF file that I have made to a certain target - In
> that respect I wish to see whats going on "inside" the GDB, so I'm using GDB
> to debug itself - Only thing is, that I don't know how this is done.
> I'm using GDB 5.0 to debug GDB 5.2.1, but how do I break or step the GDB when
> I have started the GDB being debugged? - The debugged GDB has control of the
> console. Is there any way I can use another console for debugging, or is there
> another way to do this?.
>
> Cheers,
>
> J.S.
>
next prev parent reply other threads:[~2002-11-14 14:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 6:13 James Sampson
2002-11-14 6:58 ` Tim Combs [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-31 16:17 Rajesh Warange
2006-08-31 16:34 ` Daniel Jacobowitz
2006-08-31 17:43 ` Michael Snyder
2006-08-31 21:24 ` Andreas Schwab
2006-08-31 22:54 ` Michael Snyder
2002-11-15 0:51 James Sampson
2002-02-01 8:25 Debugging gdb with gdb Salman Khilji
2002-02-01 9:26 ` Daniel Jacobowitz
2002-02-03 12:29 ` Joel Brobecker
2002-02-04 1:32 ` Christophe PLANAT
2002-02-04 12:24 ` Piet/Pete Delaney
2002-02-04 14:02 ` Kevin Buettner
2002-02-04 15:00 ` Piet/Pete Delaney
2002-02-04 15:13 ` Piet/Pete Delaney
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=20021114085605.A6694@urbana.css.mot.com \
--to=tcombs@urbana.css.mot.com \
--cc=gdb@sources.redhat.com \
--cc=i_am_triumph@ofir.dk \
/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