From: jtc@redbacknetworks.com (J.T. Conklin)
To: gdb@cygnus.com
Cc: shebs@cygnus.com, law@cygnus.com
Subject: Re: Conditionals in GDB manual
Date: Thu, 01 Apr 1999 00:00:00 -0000 [thread overview]
Message-ID: <5mg18kobd5.fsf@jtc.redbacknetworks.com> (raw)
In-Reply-To: <16950.918232591@hurl.cygnus.com>
>> I've been working over the GDB manual, and am looking at all the
>> conditionals in it; AMD29K, SPARCLET, VXWORKS, DOSHOST, POSIX, etc.
>> There are about 40 of them, and as far as I can tell, many of them
>> have never been used to make a subset manual. The exceptions are a
>> Hitachi H8-specific manual done in 1993, and more recently an HP-UX
>> specific manual, although many of the HPPA conditionals should
>> appear in the generic manual also.
>>
>> So I'm considering whacking most or all of the conditionals. This
>> won't matter to most people, because the default build/configure
>> enables almost all of these conditionals. However, if anybody has
>> a good use for a particular conditional, you'll know what it is and
>> can tell me, so that I preserve it. (I'm already discussing the
>> HPPA bits with Roz de la Torre at HP.)
> Might it make more sense to have processor specific appendices?
> We need somewhere to put processor/os specific stuff.
Ideally, there would be One True GDB Manual that contained all
information for all hosts and targets, organized in such a way so
environment specific information could be identified and located
easily by readers. Appendicies for both host and target specific
information might be a good way to accomplish this.
The many conditionals that select parts of the "Remote Debugging"
chapter seem to go along with this idea, although the individual
sections don't share the same outline of sub-sections and moving
them to an appendix might be a bit more of an overhaul than is
envisioned.
As removing the conditionals doesn't preclude a more comprehensive
edit later, I'd be in favor of it.
--jtc
--
J.T. Conklin
RedBack Networks
next prev parent reply other threads:[~1999-04-01 0:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199902050402.UAA16377@cygint.cygnus.com>
1999-04-01 0:00 ` Jeffrey A Law
1999-04-01 0:00 ` J.T. Conklin [this message]
1999-04-01 0:00 ` Stan Shebs
1999-04-01 0:00 ` Stan Shebs
1999-04-01 0:00 Stan Shebs
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=5mg18kobd5.fsf@jtc.redbacknetworks.com \
--to=jtc@redbacknetworks.com \
--cc=gdb@cygnus.com \
--cc=law@cygnus.com \
--cc=shebs@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