From owner-freebsd-current Sun Feb 2 14:43:49 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BE3C37B401 for ; Sun, 2 Feb 2003 14:43:48 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 715FE43F75 for ; Sun, 2 Feb 2003 14:43:47 -0800 (PST) (envelope-from phk@freebsd.org) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id h12MhjYu001617 for ; Sun, 2 Feb 2003 23:43:46 +0100 (CET) (envelope-from phk@freebsd.org) To: current@freebsd.org Subject: How to debug double-faults in i386 ? From: Poul-Henning Kamp Date: Sun, 02 Feb 2003 23:43:45 +0100 Message-ID: <1616.1044225825@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm getting double-faults on my laptop, and I have managed to capture them in DDB because I roughly know when to expect them. But It seems that the panic and DDB offers absolutely no helpful information about a double-fault ? How does one debug problems like this ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message