From: W.F.J.Mueller@gsi.de (Walter F.J. Mueller)
Subject: [pups] hyperlinked 2.11bsd source code
Date: Mon, 19 Feb 2007 22:06:58 +0100 [thread overview]
Message-ID: <45DA1172.3060101@gsi.de> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1625 bytes --]
to all 2.11bsd users:
when searching through the 2.11bsd code I wanted many times
a hyperlinked and cross referenced rendition of the sources,
much like doxygen or lxr does it. For kernel, lib and user
code, for c and assembler.
Since none of the existing tools seemed to do what I wanted
I wrote a perl script generating such a html'ized version of
the source code.
The tool far from finished, but starts to be useful. The
results from what I'd call an early alpha version are now
available. Just start with either the tar source
http://www-linux.gsi.de/~mueller/test/211bsd/usr/src/bin/tar.c.html
or the kernel init routine
http://www-linux.gsi.de/~mueller/test/211bsd/usr/src/sys/sys/init_main.c.html
and click a little around. The style sheet is still the debug
version, not all links end where they should.
The cross reference sections aren't complete, but already
useful. To see for example who is using setjmp see
http://www-linux.gsi.de/~mueller/test/211bsd/usr/src/lib/libc/pdp/gen/setjmp.s.html#xref:s:_setjmp
or who is including nlist.h see
http://www-linux.gsi.de/~mueller/test/211bsd/usr/include/nlist.h.html#xref:i:nlist.h
The background color tells you in which territory you are in
magenta boot and standalone code
red kernel
orange network code (running in supervisor)
green libraries
blue user level code
Hope you enjoy it.
With best regards,
Walter
--
Dr. Walter F.J. Müller Mail: W.F.J.Mueller at gsi.de
GSI, Abteilung KP3 Phone: +49-6159-71-2766
D-64291 Darmstadt FAX: +49-6159-71-3762
URL: http://www-linux.gsi.de/~mueller/
reply other threads:[~2007-02-19 21:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=45DA1172.3060101@gsi.de \
--to=w.f.j.mueller@gsi.de \
/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).