From owner-freebsd-current  Mon Mar 27 12: 2:23 2000
Delivered-To: freebsd-current@freebsd.org
Received: from overcee.netplex.com.au (peter1.yahoo.com [208.48.107.4])
	by hub.freebsd.org (Postfix) with ESMTP id BC2F637BA42
	for <freebsd-current@FreeBSD.ORG>; Mon, 27 Mar 2000 12:02:18 -0800 (PST)
	(envelope-from peter@netplex.com.au)
Received: from netplex.com.au (localhost [127.0.0.1])
	by overcee.netplex.com.au (Postfix) with ESMTP
	id 8B8C21CD9; Mon, 27 Mar 2000 12:02:07 -0800 (PST)
	(envelope-from peter@netplex.com.au)
X-Mailer: exmh version 2.1.1 10/15/1999
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: Greg Lehey <grog@lemis.com>, Brad Knowles <blk@skynet.be>,
	FreeBSD-CURRENT Mailing List <freebsd-current@FreeBSD.ORG>
Subject: Re: INVARIANTS doesn't work? 
In-Reply-To: Message from Matthew Dillon <dillon@apollo.backplane.com> 
   of "Fri, 24 Mar 2000 10:02:46 PST." <200003241802.KAA14776@apollo.backplane.com> 
Date: Mon, 27 Mar 2000 12:02:07 -0800
From: Peter Wemm <peter@netplex.com.au>
Message-Id: <20000327200207.8B8C21CD9@overcee.netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Matthew Dillon wrote:
> :Is there any good reason why we have two different options if they can
> :only be used together?
> :
> :Greg
> 
>     I think it's so you can compile a kernel with INVARIANT_SUPPORT in
>     in order to support dynamic load modules which may have been compiled
>     with INVARIANTS.

Or so that you can compile individual files with INVARIANTS by whatever
means suits your needs.  I'm aware of quite a few machines that run with
#define INVARIANTS 1  near the top of kern_malloc.c.

Cheers,
-Peter



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