public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Stephen Smith <ischis2@home.com>
To: Michael Elizabeth Chastain <chastain@cygnus.com>
Cc: gdb@sourceware.cygnus.com
Subject: Re: How do you use GDB to debug GDB
Date: Wed, 21 Mar 2001 15:59:00 -0000	[thread overview]
Message-ID: <3AB6978B.617AC2F3@home.com> (raw)
In-Reply-To: <200103192052.MAA08643@bosch.cygnus.com>

Michael Elizabeth Chastain wrote:

> Hello Stephen,
>
> This is how I do it:
>
>   [top] break help_command
>   [top] run
>
> The third line sets a convenient breakpoint in the superior gdb so that
> you can bounce back up to it.  I usually do "help foo" instead of "help"
> for getting to the superior gdb, to reduce the screen output.
>

Ok, so how do I active "help_command"

It doesn't appear to be by accessing help

sps

  parent reply	other threads:[~2001-03-21 15:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-21 15:59 Michael Elizabeth Chastain
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59   ` Andrew Cagney
2001-03-21 15:59     ` Eli Zaretskii
2001-03-21 15:59     ` Merging manuals (was Re: How do you use GDB to debug GDB) Stan Shebs
2001-03-21 15:59       ` Eli Zaretskii
2001-03-21 15:59       ` J.T. Conklin
2001-03-21 15:59         ` Eli Zaretskii
2001-03-21 15:59         ` Michael Meissner
2001-03-21 15:59   ` How do you use GDB to debug GDB Kevin Buettner
2001-03-21 15:59 ` Stephen Smith [this message]
2001-03-21 15:59 ` Stephen Smith
  -- strict thread matches above, loose matches on Subject: below --
2001-03-21 15:59 Michael Elizabeth Chastain
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 Michael Elizabeth Chastain
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 Stephen Smith
2001-03-21 15:59 ` J.T. Conklin
2001-03-21 15:59 ` Fernando Nasser
2001-03-21 15:59   ` Frank Ch. Eigler
2001-03-21 15:59     ` Christopher Faylor

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=3AB6978B.617AC2F3@home.com \
    --to=ischis2@home.com \
    --cc=chastain@cygnus.com \
    --cc=gdb@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).