From mint-bounce@lists.fishpool.fi Mon Jan 11 09:52:20 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=doeC5Sr5WEbPusiV2pGDvtRkrI1jjCpHpwoDx0jG2VQ=; b=ikooMA6ufLCH1DZTnpCewDoAVGwV6MKv6Exd9QctfmwUtv84+f+J4VpNz1vsNqcdWb ZrXoECIh6IIRekpuKlGHU7j0rld5xB+CKvzPOvT/wC+1TdAY9g59BlULNj+YnfggDDpw l3tHOVw8CRvE7xkq8lfUejsEE9bxjWzY7tr04= 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=jQ6b5L4O3YLyZB4+c1PqWgDH5sOVJ8MS9N9eaJij0ktkE+bbd9zqT3xOck6zkOBe8b mT8m2XPGk7Hk513fs8j0nQtV1eRQpVTUzDkYW1+1YlEoHAxSlz3qtPQpGsYV/JJVp/J/ oWt0iXPXdhNxDFasLKu/v/jWDXSMmKf0pXabY= MIME-Version: 1.0 In-Reply-To: <4B4B344B.1060306@freesbee.fr> References: <4B477F2C.4020503@freesbee.fr> <4B4780E8.3050503@atari-source.org> <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> Date: Mon, 11 Jan 2010 15:50:08 +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=0015175ce22650a141047ce4a7c8 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: --0015175ce22650a141047ce4a7c8 Content-Type: text/plain; charset=ISO-8859-1 > > No, it is not triggered by sed. > In my case it was triggered by make. > The makefile was using "which" and "sed". > Hmm... it's very sad we can't properly spot the exact situation when it happens but if we are more or less sure it happens in larger builds, what about of compilation of freemint kernel in debug mode and try it again? In this way we could log every malloc(size) calls and in the same time we could log response from freemint kernel. So if you Mark or Keith or anyone have setup suitable for some large build, it is in my opinion worth of trying, especially in aranym environment where you can redirect all debug (trace) output to console -- if the crash occurs, we'll have exact log of all (k)mallocs and (k)frees and probably, with some luck, we will be able to simulate it from simple C test case. -- MiKRO / Mystic Bytes http://mikro.atari.org --0015175ce22650a141047ce4a7c8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
No, it is not tr= iggered by sed.
In my case it was triggered by make.
The makefile was using "which" and "sed".
Hmm... it's very sad we can't properly spot the exact situa= tion when it happens but if we are more or less sure it happens in larger b= uilds, what about of compilation of freemint kernel in debug mode and try i= t again? In this way we could log every malloc(size) calls and in the same = time we could log response from freemint kernel. So if you Mark or Keith or= anyone have setup suitable for some large build, it is in my opinion worth= of trying, especially in aranym environment where you can redirect all deb= ug (trace) output to console -- if the crash occurs, we'll have exact l= og of all (k)mallocs and (k)frees and probably, with some luck, we will be = able to simulate it from simple C test case.


--
MiKRO / Mystic Bytes
http://mikro.atari.org
--0015175ce22650a141047ce4a7c8--