From mint-bounce@lists.fishpool.fi Mon Jan 11 04:39:32 2010 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=EtbOZRbZIDkdPpJcrOFNmpuyzNVVlaYuosnOGzQ9d+M=; b=scziA5xE1z/frckvEeZ+qTmO0Y12dXPkcADNeiwJOzVhYH5cCwmhF2PVS68OuikOJ+ ZrqWu3uYi6ASJE6WlygXBo7K3KOEK0UvV9basf93Ey3B7JQ+HAqYsfPemFx7J3a/QOqb FXfaKzgm8zmeBydxPVDIwIzh/z5g39Ay3JzsE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=qDKUgd3Wc5N97NE3+NZSYWxJ9QiTnk2v5oq+eZDEDd2AZVm9vHkSferV6zB9XJYkaT 5/NuPKoa7ycRDu+aZ8NBxnOaPk/vq3zxEJkJBXntjHcZo4HHsUbh7ZYCqjw0miurmEAC BYMm6g9HVUEZllcRy8BHqwtfTmgHzT6J3Mqeg= Message-ID: <4B4AF146.7090603@freesbee.fr> Date: Mon, 11 Jan 2010 10:37:10 +0100 From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: mint Subject: Re: [MiNT] malloc() bug ? References: <4B477F2C.4020503@freesbee.fr> <4B4780E8.3050503@atari-source.org> <4B47BAC9.2080000@freesbee.fr> <4B47BBFB.2040206@atari-source.org> <11a6f2b11001102254s5bbca91am42472d701646ed2c@mail.gmail.com> In-Reply-To: <11a6f2b11001102254s5bbca91am42472d701646ed2c@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: vincent.riviere@freesbee.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Paul Wratt wrote: > Tis a guess really, but is there any (logical) reason as to why there > should be an issue regarding memory usage and management, ONLY on long > or large compiles (or makes)? Last time it occurred for me it was a very short test makefile, with no gcc call, only multiple calls to "which" and "sed". I had copy/pasted these lines 6 or 7 times to simulate a big activity, and the malloc bug appeared. Unfortunately I didn't backup that simple makefile :-( It is sure that the "make" command from SpareMiNT contains the malloc bug. However I didn't run MiNT with memory protection, maybe some other process (which, sed or other) has overwritten the make memory. This is really annoying. -- Vincent Rivière