From owner-freebsd-current Mon Mar 3 15:36:44 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1D7737B401; Mon, 3 Mar 2003 15:36:43 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0134743F3F; Mon, 3 Mar 2003 15:36:43 -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.12.8/8.12.8) with ESMTP id h23NagG1028885 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 3 Mar 2003 18:36:42 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id h23Nab871910; Mon, 3 Mar 2003 18:36:37 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15971.59141.326652.334367@grasshopper.cs.duke.edu> Date: Mon, 3 Mar 2003 18:36:37 -0500 (EST) To: jhb@freebsd.org Cc: freebsd-current@freebsd.org Subject: witness_get: witness exhausted? X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm developing a character driver which tracks a lot of state on a per-open basis. I've got several mutexes in there which are initialzed at open, and destroyed at close. After a few dozen opens, witness seems to croak with: witness_get: witness exhausted Am I leaking something? Or is the witness code? I looked at subr_witness.c, and I don't see witness_free() being called from witness_destroy(). There's probably some design constraint that I don't understand. If the fault is with the witness code, can it be fixed? FWIW, Witness (and the FreeBSD debugging environment in general) is why I've gotten approval to co-develop this driver on FreeBSD (in addition to linux). Its already caught several locking bugs. Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message