> However, trying to use them with a kernel built with debugging symbols
> fails with "Data Access Exception" (sometimes "Instruction Access
> Exception") whilst it's going through the symbol table.  Maybe the size
> of a kernel with full debug symbols is just too much for it.  I haven't
> even attempted to look closely at it yet.
> 
Depending on the type of memory installed in the machine you may have
only 4MB available in the lowest contiguous address range. A kernel
compiled with `-g' entirely may well be much larger than 4MB.


> Whilst I've got fingers to keyboard, should ddb be able to resolve
> addresses in a trace if you've booted across the network (and thus
> are using a SunOS boot block)?  Whenever my machine panics, it drops
> down to ddb but typing "trace" doesn't give any useful stack trace.

The (second stage) boot program is responsible for loading the symbols
so ddb can find them. You'll need the NetBSD boot program for this, but
it doesn't do network bootstrapping yet.

-pk