From owner-freebsd-bugs Wed Jan 15 10:21:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA15334 for bugs-outgoing; Wed, 15 Jan 1997 10:21:33 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA15304; Wed, 15 Jan 1997 10:20:54 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id FAA32039; Thu, 16 Jan 1997 05:18:32 +1100 Date: Thu, 16 Jan 1997 05:18:32 +1100 From: Bruce Evans Message-Id: <199701151818.FAA32039@godzilla.zeta.org.au> To: bugs@freebsd.org Subject: panic("vm_fault: fault on nofault entry...") in ddb Cc: dyson@freebsd.org Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The "fault on nofault entry" panic is fairly easy to run in to by attempting to examine nonexistent memory using ddb. The panic defeats ddb's trap handler. I got it for examining some sort of ffs buffer being copied out: x/x 0xf28f9000,1000 1000 was supposed to be a lazy way to get to the end, but is 4 times to large. Bruce