Messages in this thread | | | From | Peter Steiner <> | Date | Thu, 7 Sep 2000 12:08:41 +0200 | Subject | Re: Availability of kdb |
| |
Gregory Maxwell <greg@linuxpower.cx> wrote:
>If this is your primary argument for a kernel debugger, a 'crash dump tool >with extra controls', then why not just cleanly implement a 'crash dump >tool with extra controls'.
What about an enhanced printk tool that virtually inserts conditional printk's into the kernel without the need to recompile the kernel? Logpoints, conditions and what to print could be set with a usermode tool. And there should be an emergency stop keycombination that clears all logpoints. That's all.
Activating logging should be as easy as feeding an email into the usermode tool. And a second tool could automatically prepare an email with the results.
Peter -- _ x ___ p.steiner@t-online.de (Peter Steiner) / \_/_\_ /,--' Linux User #55148 (http://counter.li.org/) \/>'~~~~// \_____/ perl -e'while(<>){s/=\n//g;s/=([\dA-F]{2})/chr(hex($1))/eg;print;}' - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
| |