From owner-freebsd-hackers Sat Jan 30 10:53:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24345 for freebsd-hackers-outgoing; Sat, 30 Jan 1999 10:53:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles119.castles.com [208.214.165.119]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24334; Sat, 30 Jan 1999 10:53:29 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id KAA01025; Sat, 30 Jan 1999 10:49:39 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901301849.KAA01025@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Luigi Rizzo cc: hackers@FreeBSD.ORG, phk@FreeBSD.ORG Subject: Re: "warning: malloc wrapped" In-reply-to: Your message of "Fri, 29 Jan 1999 09:53:44 +0100." <199901290853.JAA12795@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 30 Jan 1999 10:49:38 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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