From owner-freebsd-hackers  Wed Mar 19 17:51:23 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA12527
          for hackers-outgoing; Wed, 19 Mar 1997 17:51:23 -0800 (PST)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA12517
          for <hackers@FreeBSD.ORG>; Wed, 19 Mar 1997 17:51:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id RAA18256; Wed, 19 Mar 1997 17:52:29 -0800 (PST)
Message-Id: <199703200152.RAA18256@root.com>
X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol
To: dennis <dennis@etinc.com>
cc: hackers@FreeBSD.ORG
Subject: Re: insight on malloc crash... 
In-reply-to: Your message of "Wed, 19 Mar 1997 19:04:57 EST."
             <3.0.32.19970319190454.00b222d0@etinc.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Wed, 19 Mar 1997 17:52:29 -0800
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 :/

   The only thing that comes to mind off-hand is that "size" might be
bogus (either 0 or way too large). Is the panic on the first byte zeroed,
or is it some amount into the malloced area?

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project