9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <russcox@gmail.com>
To: 9fans@cse.psu.edu
Subject: [9fans] more plan 9 ports, including acid
Date: Mon, 19 Apr 2004 22:52:05 -0400	[thread overview]
Message-ID: <EB4D8D69.7E7E90E6@mail.gmail.com> (raw)

There are a lot of changes available in the CVS repository
for the Plan 9 ports tree.  There is also a new tarball.

Among the changes:

	- 9term won't echo passwords anymore (thanks to
		Axel Belinfante)
	- UTF8 input support (thanks to David Tolpin)
	- added comm, gzip, bzip2, look, plot, graph
		(thanks to Taj Khattra)
	- many little fixes to rio (thanks to Axel Belinfante)
	- added htmlfmt (thanks to William Josephson)
	- added fmt, tweak
	- a first stab at some manual pages

The biggest new piece is db and acid, though they're
not quite as portable as I would like.  They run on all
the supported systems, but they're only really useful for 
debugging FreeBSD and Linux x86 binaries at the moment.
(That is, you can debug x86 binaries on any supported
system.)  OtherBSD x86 binary support should be easy to add.
The Mac OS part is done except that stack traces are
very hard and not implemented -- you can look at binaries
and data, just not stack traces.  Adding support for SunOS
binaries is probably easy if you understand register windows,
which I don't.

Acid works well enough on the x86 systems to debug
multithreaded programs using -lthread.  It handles
dynamic libraries reasonably and uses the stabs or
dwarf type info embedded in the binaries being debugged.
The acid(1) man page has some high-level details.
You don't really want to know the low-level details.

/usr/local/plan9/src/acid/Notes details the changes
to the acid language that didn't fit into the man page.
(I haven't updated philw's manual.)

Enjoy.
Russ


             reply	other threads:[~2004-04-20  2:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-20  2:52 Russ Cox [this message]
2004-04-20 12:58 ` Ishwar Rattan
2004-04-20 13:27   ` Russ Cox
2004-04-20 14:53     ` Joel Salomon

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=EB4D8D69.7E7E90E6@mail.gmail.com \
    --to=russcox@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).