From mint-bounce@lists.fishpool.fi Mon Jan 11 09:59:27 2010 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=aK2+e370ZHFXLmMf5cxFeBACyGBZi2M7RrvWXnqvYrs=; b=MmJpcWFIknDRjKHPJgHl+1SV41DuAaCNJocmq9IzH2Tw5kVyPJPEHFivRMOyK7naMP sqU+SXp9BoaSebzte2jC+CBC/oEHq04Fv/ge2OnyYPsNo2FrwsEBpieiwNk5aADSJKe4 HsE+LbmS9rewtaxSxFk1ju5T3/zYzBORDNm1g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=o2vcJkDbGq/YPmB2wWOLnrkOB+Y2VrOnVuh8IEalSWyvEVIQp6b7YePfIbbnOL2UDJ bPQKWGG3+xbVMPSzGaUikxpksvLEx1zdezUvWkdllbHJaRMaEMmaUBNcgpUBlF8SK2hP nEAyR0uY6uwN58jAVOkNG8qrb8YgcAhPDyWpE= MIME-Version: 1.0 In-Reply-To: <4B4B3B51.9000605@freesbee.fr> References: <4B477F2C.4020503@freesbee.fr> <4B47BAC9.2080000@freesbee.fr> <4B47BBFB.2040206@atari-source.org> <11a6f2b11001102254s5bbca91am42472d701646ed2c@mail.gmail.com> <4B4AF146.7090603@freesbee.fr> <11a6f2b11001110444m665fcc8p11af912c7514686c@mail.gmail.com> <4B4B3333.4050802@atari-source.org> <4B4B344B.1060306@freesbee.fr> <4B4B3B51.9000605@freesbee.fr> Date: Mon, 11 Jan 2010 15:57:17 +0100 Message-ID: Subject: Re: [MiNT] malloc() bug ? From: Miro Kropacek To: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= Cc: mint@lists.fishpool.fi Content-Type: multipart/alternative; boundary=000325558c16ed12d7047ce4c007 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: miro.kropacek@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: --000325558c16ed12d7047ce4c007 Content-Type: text/plain; charset=ISO-8859-1 > > Doing that in the MiNTLib should be enough. > I'm not sure if you're right -- kernel has much more trace outputs, so we can see some special condition has happened (for example allocation 1 byte behind page boundary, N bytes long biggest available block, number of block or anything else, I'm just guessing). But of course, debug mintlib + debug kernel may be the best option. -- MiKRO / Mystic Bytes http://mikro.atari.org --000325558c16ed12d7047ce4c007 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Doing that in th= e MiNTLib should be enough.
I'm not sure if you= 9;re right -- kernel has much more trace outputs, so we can see some specia= l condition has happened (for example allocation 1 byte behind page boundar= y, N bytes long biggest available block, number of block or anything else, = I'm just guessing). But of course, debug mintlib + debug kernel may be = the best option.


--
MiKRO / Mystic Bytes
http://mikro.atari.org
--000325558c16ed12d7047ce4c007--