From owner-freebsd-hackers  Wed Mar 19 16:05:53 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA03323
          for hackers-outgoing; Wed, 19 Mar 1997 16:05:53 -0800 (PST)
Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA03316
          for <hackers@freebsd.org>; Wed, 19 Mar 1997 16:05:48 -0800 (PST)
Received: from ntws (ntws.etinc.com [204.141.95.142]) by etinc.com (8.8.3/8.6.9) with SMTP id TAA11834 for <hackers@freebsd.org>; Wed, 19 Mar 1997 19:09:42 -0500 (EST)
Message-Id: <3.0.32.19970319190454.00b222d0@etinc.com>
X-Sender: dennis@etinc.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Wed, 19 Mar 1997 19:04:57 -0500
To: hackers@freebsd.org
From: dennis <dennis@etinc.com>
Subject: insight on malloc crash...
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Can anyone give some insight on why the following code might
panic v2.2 (while it has been working happily since 1.x)

p=malloc(size,M_DEVBUF,M_WAITOK);
if (p)
	bzero(p,size)


bzero is panicing....did something change? this stuff isnt very
well document :/

Dennis