From: wkt@tuhs.org (Warren Toomey)
Subject: [TUHS] Scan of "Edition 0" manual
Date: Wed, 27 Jan 2016 09:46:48 +1000 [thread overview]
Message-ID: <20160126234648.GA833@minnie.tuhs.org> (raw)
In-Reply-To: <20160126231553.GA29644@minnie.tuhs.org>
On Sun, Dec 27, 2015 at 12:09:03AM +1000, Warren Toomey wrote:
> > http://www.tuhs.org/Archive/PDP-11/Distributions/research/McIlroy_v0/UnixEditionZero.txt
> >
> > Doug, page A7 is missing. Could you e-mail in a scan of that page?
>
> Doug reports in a private e-mail that the physical page A7 is missing,
> so he is unable to scan it in. Oh well.
Actually, we can probably substitute part of the db(1) man page from 1st
Edition Unix for the missing page A7:
= When preceded by an expression, the value of the
expression is typed in octal. When not preceded by an
expression, the value of. "." is indicated. This
command does not change the value of ".".
: An attempt is made to print the given expression as a
symbolic address. If the expression is relocatable,
that symbol is found whose value is nearest that of
the expression, and the symbol is typed, followed by a
sign and the appropriate offset. If the value of the
expression is absolute, a symbol with exactly the
indicated value is sought and printed if found; if no
matching symbol is discovered, the octal value of the
expression is given.
The following command may be used to patch the file being
debugged.
! This command must be preceded by an expression. The
value of the expression is stored at the location
addressed by the current value of "." . The opcodes do
not appear in the symbol table, so the user must
assemble them by hand.
The following command is used after a fault has caused a core
image file to be produced.
$ causes the contents of the general registers and
several other registers to be printed both in octal
and symbolic format. The values are as they were at
the time of the fault.
The only way to exit from db is to generate an end of file
on the typewriter (EOT character).
Cheers, Warren
next prev parent reply other threads:[~2016-01-26 23:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 1:55 [TUHS] " Doug McIlroy
2015-11-24 2:57 ` Warren Toomey
2015-11-24 3:55 ` arnold
2015-11-24 6:41 ` Random832
2015-11-28 23:24 ` [TUHS] Scan of " Warren Toomey
2015-11-29 2:01 ` Warren Toomey
2015-11-29 14:31 ` Clem cole
2015-11-29 20:21 ` Christian Neukirchen
2015-11-29 20:40 ` Nelson H. F. Beebe
2015-11-29 21:45 ` arnold
2015-11-30 4:02 ` John Cowan
2015-11-30 4:26 ` Dave Horsfall
2015-12-26 14:09 ` Warren Toomey
2016-01-26 23:15 ` Warren Toomey
2016-01-26 23:46 ` Warren Toomey [this message]
2015-11-29 17:51 Nelson H. F. Beebe
2015-11-29 20:00 ` Warren Toomey
[not found] <mailman.3.1448845201.3730.tuhs@minnie.tuhs.org>
[not found] ` <353E052F-541F-47C1-9ACF-587EB9EC6088@mcjones.org>
2015-11-30 9:06 ` Warren Toomey
2015-12-01 21:48 ` Random832
2015-12-01 22:29 ` Dave Horsfall
2015-12-02 0:44 ` Random832
2015-12-02 17:21 ` shawn wilson
2015-12-02 18:32 ` Random832
2015-12-08 18:20 Doug McIlroy
2015-12-08 18:47 ` Charles Anthony
2015-12-08 18:57 ` Marc Rochkind
2015-12-08 19:16 ` John Cowan
2016-01-27 3:01 Doug McIlroy
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=20160126234648.GA833@minnie.tuhs.org \
--to=wkt@tuhs.org \
/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 NNTP newsgroup(s).