From: Kevin Buettner <kevinb@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>,
Michael Elizabeth Chastain <chastain@cygnus.com>
Cc: gdb@sourceware.cygnus.com, ischis2@home.com
Subject: Re: How do you use GDB to debug GDB
Date: Wed, 21 Mar 2001 15:59:00 -0000 [thread overview]
Message-ID: <1010320162302.ZM10111@ocotillo.lan> (raw)
In-Reply-To: <Pine.SUN.3.91.1010320111702.7756K-100000@is>
On Mar 20, 11:17am, Eli Zaretskii wrote:
> One thing puzzles me, though: why is the section "Debugging GDB with
> itself" in gdbint.texinfo instead of gdb.texinfo? Is there any reason
> not to move (or copy) it to gdb.texinfo?
Presumably there's little reason for the average user to want to
debug GDB (with itself). Therefore it's more suitable for such
material to appear in the internals document...
Kevin
next prev 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 ` Stephen Smith
2001-03-21 15:59 ` Stephen Smith
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 ` Kevin Buettner [this message]
2001-03-21 15:59 ` Andrew Cagney
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 Eli Zaretskii
-- 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 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
2001-03-21 15:59 Michael Elizabeth Chastain
2001-03-21 15:59 ` Eli Zaretskii
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=1010320162302.ZM10111@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=chastain@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb@sourceware.cygnus.com \
--cc=ischis2@home.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