From: Eli Zaretskii <eliz@is.elta.co.il>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Michael Elizabeth Chastain <chastain@cygnus.com>,
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: <Pine.SUN.3.91.1010321115003.24397M-100000@is> (raw)
In-Reply-To: <3AB78AA3.A534B844@cygnus.com>
On Tue, 20 Mar 2001, Andrew Cagney 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? Can some of the elders
> > please shed some light on this?
>
> To expand a little on Michael's comment.
>
> gdbint.texinfo is for internals - the things you see when you lift the
> bonnet (1) and start poking around with the engine.
Exactly. And, at least in my opinion, a collection of user-level
tricks useful for debugging a specific program called `gdb' is not
exactly ``what you see under the hood''.
> As a complete asside, it has also been suggested that the two documents
> be merged. From memory GCC did this.
How about if we do that for 5.1? Shouldn't be too hard, I think.
OTOH, the GCC manual leaves a lot to be desired (IMHO), so perhaps we
shouldn't follow their lead without thinking real hard.
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 ` Eli Zaretskii
2001-03-21 15:59 ` Andrew Cagney
2001-03-21 15:59 ` Eli Zaretskii [this message]
2001-03-21 15:59 ` Merging manuals (was Re: How do you use GDB to debug GDB) Stan Shebs
2001-03-21 15:59 ` J.T. Conklin
2001-03-21 15:59 ` Michael Meissner
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 ` How do you use GDB to debug GDB Kevin Buettner
2001-03-21 15:59 ` Stephen Smith
2001-03-21 15:59 Stephen Smith
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 ` J.T. Conklin
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
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=Pine.SUN.3.91.1010321115003.24397M-100000@is \
--to=eliz@is.elta.co.il \
--cc=ac131313@cygnus.com \
--cc=chastain@cygnus.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).