From owner-freebsd-alpha  Mon Mar 26 17: 5:21 2001
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1995D37B71B; Mon, 26 Mar 2001 17:05:18 -0800 (PST)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id UAA29245;
	Mon, 26 Mar 2001 20:05:16 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2R14kv68429;
	Mon, 26 Mar 2001 20:04:46 -0500 (EST)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15039.59182.857539.804159@grasshopper.cs.duke.edu>
Date: Mon, 26 Mar 2001 20:04:46 -0500 (EST)
To: obrien@FreeBSD.ORG
Cc: alpha@FreeBSD.ORG
Subject: Re: dump(8)
In-Reply-To: <20010326170253.A45531@dragon.nuxi.com>
References: <20010326170253.A45531@dragon.nuxi.com>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


David O'Brien writes:
 > This broken dump(8) situation *must* get fixed.  It is time to back out
 > commits.  Does anyone have any idea what commit(s) broke dump?

Nope.

Its almost certainly related to the linuxthreads problem I was talking
about last week where a userland app dies on an instruction fault
with a PC somwhere in witness_exit().

I haven't been able to figure it out yet..


Drew

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message