> As it is, the symbol table is always loaded in at boot time.  Currently
> it's thrown away early if DDB is not present, but there's no reason it
> can't be kept around until kvm_mkdb is run.

unfortunately, i don't see this as being particularly feasible:
	(1) kvm_mkdb *can* be run multiple times
	(2) how do you make it machine independent?
	(3) how do you find the symbols to begin with?

(3) and (2) are closely tied together, and coule be fatal.
(1) definitely is a problem, unless you're always willing to keep the
symbols around (and in so doing waste a lot of RAM in non-ddb kernels;
see the 2M machine again).



chris


------------------------------------------------------------------------------