On Sun, Sep 03, 2006 at 11:45:15AM -0500, Jacob Yocom-Piatt wrote: > i've been adding code to sys/dev/vnd.c and have panicked a kernel that is > recompiled with these changes. i have a few questions related to this issue: > > - is there a way to avoid having to recompile the whole kernel when making > edits > to only a single file? i'm accustomed to the config, make clean, make depend, > make cycle and want to speed things up.
Guess why make was invented. Yes you can, just "make" :) > > - am i correct in saying you cannot "update" the kernel while it is running, > i.e. avoid rebooting everytime a new kernel is compiled? yes, doesn't work (unless you use some emulator ;)) > > - is it possible to get line numbers of the source that panicked the kernel? > when using gcc and gdb with the -g switch it is much easier to debug code. It's possible to built gdb support into the kernel. NetBSD has a "howto" that works 1:1 with OpenBSD. [1] > > - the "info gdb" docs provide a wealth of examples that are very illustrative. > is there something analogous for ddb? > Maybe [2] this is helpful? Other than that, i don't know. > these questions may seem silly to those who already know the answers, so > please > don't club me too harshly. > > cheers, > jake > > Tobias [1] http://netbsd.org/Documentation/kernel/kgdb.html [2] http://www.benzedrine.cx/crashreport.html
