From: Michael Snyder <msnyder@specifix.com>
To: Ray Hurst <rhurst2@cox.net>
Cc: gdb@sources.redhat.com
Subject: Re: How do you debug gdb?
Date: Tue, 19 Feb 2008 20:19:00 -0000 [thread overview]
Message-ID: <1203449896.19253.165.camel@localhost.localdomain> (raw)
In-Reply-To: <fpavs9$sa7$1@ger.gmane.org>
On Sun, 2008-02-17 at 20:00 -0800, Ray Hurst wrote:
> It seemed that this question was better suited for the development group
> than in the general group.
>
> How do you debug gdb?
>
> In other words, if I have a problem with gdb itself how do I go about
> debugging the issue?
It's a little counter intuitive, but just as you compile GCC
with GCC, you also debug GDB with GDB.
After all, GDB is just a program...
If you do it in the build directory, you will find that
there is already some infrastructure in place. See the
existing file ".gdbinit", which sets some breakpoints
and changes the prompt.
Changing the prompt is perhaps the number one
most important thing to do --- that way you can
tell by looking at the prompt whether you are
talking to the gdb-being-debugged or to the
gdb-doing-the-debugging.
next prev parent reply other threads:[~2008-02-19 19:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 5:08 Ray Hurst
2008-02-18 8:54 ` Fabian Cenedese
2008-02-18 9:04 ` Gerrit van Niekerk
2008-02-19 20:19 ` Michael Snyder [this message]
2008-02-19 21:50 ` Doug Evans
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=1203449896.19253.165.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=gdb@sources.redhat.com \
--cc=rhurst2@cox.net \
/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