From owner-freebsd-hackers  Wed Aug 13 09:39:49 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id JAA11605
          for hackers-outgoing; Wed, 13 Aug 1997 09:39:49 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA11563;
          Wed, 13 Aug 1997 09:39:37 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA12554; Wed, 13 Aug 1997 09:34:38 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199708131634.JAA12554@phaeton.artisoft.com>
Subject: Re: 2.2.2+ crash.. more info
To: dg@root.com
Date: Wed, 13 Aug 1997 09:34:38 -0700 (MST)
Cc: julian@FreeBSD.ORG, hackers@FreeBSD.ORG
In-Reply-To: <199708130443.VAA07651@implode.root.com> from "David Greenman" at Aug 12, 97 09:43:13 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>    Quite likely. It's fairly easy to have a bug where a resource is exhausted
> (usually memory) in a subroutine called from an interrupt routine, resulting
> in a tsleep() if the call to malloc isn't M_NOWAIT.

Is there any way we could talk you into adding an #ifdef DIAGNOSTIC
to malloc to catch this case?


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.