From owner-freebsd-stable  Tue Nov 30 10:15:53 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226])
	by hub.freebsd.org (Postfix) with ESMTP id 429071599F
	for <freebsd-stable@freebsd.org>; Tue, 30 Nov 1999 10:15:32 -0800 (PST)
	(envelope-from dgilbert@trooper.velocet.net)
Received: (from dgilbert@localhost)
	by trooper.velocet.net (8.9.3/8.9.3) id NAA29120;
	Tue, 30 Nov 1999 13:15:31 -0500 (EST)
	(envelope-from dgilbert)
From: David Gilbert <dgilbert@velocet.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14404.5187.497998.940864@trooper.velocet.net>
Date: Tue, 30 Nov 1999 13:15:31 -0500 (EST)
To: freebsd-stable@freebsd.org
Subject: stack up or stack down.
X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs  Lucid
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I'm trying to track down where vinum is trashing the kernel stack.  It 
has been suggested that the only way to attack this it to rummage
around the stack for a valid frame.  To that end, does the kernel
stack build up (from low to high addresses) or down (high to low
addresses) in FreeBSD?

Dave.c


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