Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S271089AbTHMEks (ORCPT ); Wed, 13 Aug 2003 00:40:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S271324AbTHMEks (ORCPT ); Wed, 13 Aug 2003 00:40:48 -0400 Received: from sngrel5.hp.com ([192.6.86.210]:47827 "EHLO sngrel5.hp.com") by vger.kernel.org with ESMTP id S271089AbTHMEkr (ORCPT ); Wed, 13 Aug 2003 00:40:47 -0400 From: Martin Pool Subject: Re: KDB in the mainstream 2.4.x kernels? Date: Wed, 13 Aug 2003 14:40:31 +1000 User-Agent: Pan/0.14.0 (I'm Being Nibbled to Death by Cats!) Message-Id: References: To: Andi Kleen , linux-kernel@vger.kernel.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1048 Lines: 24 On Fri, 18 Jul 2003 22:43:57 +0200, Andi Kleen wrote: > KDB is usually not useful for debugging hangs on desktop boxes (and even > many servers) because you have usually X running. When the machine crashes > and goes in KDB you cannot see the text output and debug anything. I > learned to type "go" blind when I had still an KDB aware kernel, > but it's not very useful overall. Perhaps in the case where the console is on a vt, kdb could try to switch to the right vc before presenting its prompt? I realize calling into the vc code might be risky but it seems like there's not much to lose. (If you do have a bug in say the agp driver then you need a serial console...) If it works, you'll be able to debug and continue. It could even set the colors to white on blue. :-) -- Martin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/