From owner-freebsd-current Sun May 31 12:42:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07002 for freebsd-current-outgoing; Sun, 31 May 1998 12:42:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feldman.dyn.ml.org (root@1Cust162.tnt5.tco2.da.uu.net [153.35.91.162]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06977 for ; Sun, 31 May 1998 12:42:17 -0700 (PDT) (envelope-from green@feldman.dyn.ml.org) Received: (from root@localhost) by feldman.dyn.ml.org (8.8.8/8.8.8) id PAA04250; Sun, 31 May 1998 15:42:09 -0400 (EDT) (envelope-from green) Message-ID: <19980531154208.A4224@dyn.ml.org> Date: Sun, 31 May 1998 15:42:08 -0400 From: The Super-User To: freebsd-current@FreeBSD.ORG Subject: really bad inodedep crash Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, there goes another crash. I got a VERY strange crash, something about inodedep, by pressing ^Z during a make in a port dir; I haven't been able to recreate this crash, and the core seemed to be corrupted (or maybe the system was actually that way) because a backtrace was showing two undefined functions continually looping. I'd know more, but this vmcore got corrupted I guess :-/. Ahh well, if I can ever find something else like this again, I'll post again. BTW, this is with SoftUpdates, but a few days ago my computer DID crash with no softupdates, and only async; go figure. Brian Feldman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message