[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-hackers
Subject:    Re: "warning: malloc wrapped"
From:       Mike Smith <mike () smith ! net ! au>
Date:       1999-01-30 18:49:38
[Download RAW message or body]

> Hi,
> 
> while loading a rather large PicoBSD image (leaving only some
> 50KB free on a 1.44MB floppy; the in-kernel fs size is 2400KB) i
> get the following message:
> 
>     Booting 0:fd(0,a)kernel @ 0x333000
>     text=0x138000 data=0x0 bss=0xa00 symbols=[+0x600+0x4+0x270+0x4+0x1e2]
>     total=0x46c45a entry point=0x333000
>     Uncompressing kernel...warning: malloc wrapped
>     done
>     Booting the kernel
> 
> (this is on 2.2.X, the image is a.out format, and i see it on both
> an 8MB and a 128MB machine.)
> 
> I am concerned by the "malloc wrapped" message -- what is exactly
> happening, and can i fix it in some way ? I haven't seen any problem so
> far but it might just be that it corrupts some pieces of code/mfs that
> i have not used yet.

The malloc() pretender in the kzip code just increments a pointer 
around a small ring.  When the pointer gets back to the beginning of 
the ring, you get that message; it means that a newly allocated region 
may overlap one that was allocated before.

This is one of the reasons that kzip must die.

-- 
\\  Sometimes you're ahead,       \\  Mike Smith
\\  sometimes you're behind.      \\  mike@smith.net.au
\\  The race is long, and in the  \\  msmith@freebsd.org
\\  end it's only with yourself.  \\  msmith@cdrom.com



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

[prev in list] [next in list] [prev in thread] [next in thread]