From: Grant Edwards <grante@visi.com>
To: gdb@sources.redhat.com
Subject: Re: Debugging GDB and breaking?
Date: Wed, 18 Dec 2002 11:01:00 -0000 [thread overview]
Message-ID: <20021218125921.A9829@visi.com> (raw)
In-Reply-To: <200212181523.gBIFNUZ10382@duracef.shout.net>; from mec@shout.net on Wed, Dec 18, 2002 at 09:23:30AM -0600
On Wed, Dec 18, 2002 at 09:23:30AM -0600, Michael Elizabeth Chastain wrote:
> Some general hints for debugging gdb:
>
> I start with "gdb /my/gdb/to/debug/bin/gdb". I like to use a stable gdb
> for the top gdb, such as the vendor-supplied gdb or gdb 5.3. Also this
> helps separate, in my mind, the top gdb from the inferior gdb.
>
> Then I immediately:
>
> (gdb) set prompt [top]
> [top] break help_command
> [top] set args /program/under/test
>
> The first line distinguishes the top gdb from the inferior gdb.
Running them in separate ttys prevents confusion for me:
gdb -tty=<whatever> /my/buggy/gdb
Or I use the equivalent menu item in DDD or Insight...
--
Grant Edwards
grante@visi.com
next prev parent reply other threads:[~2002-12-18 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 7:23 Michael Elizabeth Chastain
2002-12-18 7:59 ` Andreas Schwab
2002-12-18 11:01 ` Grant Edwards [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-19 1:16 James Sampson
2002-12-18 5:49 James Sampson
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=20021218125921.A9829@visi.com \
--to=grante@visi.com \
--cc=gdb@sources.redhat.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