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. - am i correct in saying you cannot "update" the kernel while it is running, i.e. avoid rebooting everytime a new kernel is compiled? - 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. - the "info gdb" docs provide a wealth of examples that are very illustrative. is there something analogous for ddb? these questions may seem silly to those who already know the answers, so please don't club me too harshly. cheers, jake
