matthew green wrote:
   > how about modloading a routine to dump a bunch of crap you're interested in?
   
   While this is one theoretical usage, it would only be maybe useful during
   DDB development. This happens rarely :) Surely rarely enough to not
   warrant supporting this.
   
   If you just need to dump some crap, you can do it directly from
   the LKM, you don't need to hack DDB to print the value for you, you
   can install e.g. a new syscall which does the work you need.
   (Ab)Using DDB hooks for things like this seems "wrong".


i dunno, i don't agree with this.  i can imagine a situation when you send
someone else an LKM with new ddb commands.  or you're trying to debug a
system you don't want to reboot and you're already using DDB heavily for
debugging.  i can think of more reasons it might be valid.



.mrg.