From mint-bounce@lists.fishpool.fi Sun Sep 26 12:39:02 2010 Date: Sun, 26 Sep 2010 18:36:43 +0200 (CEST) From: Martin Tarenskeen X-X-Sender: m.tarenskeen@localhost6.localdomain6 To: Mark Duckworth cc: mint@lists.fishpool.fi Subject: Re: [MiNT] compile problem In-Reply-To: <4C9F60BF.7020509@atari-source.org> Message-ID: References: <4C9E58F4.1080604@freesbee.fr> <4C9F60BF.7020509@atari-source.org> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1463789311-2014241555-1285519003=:2148" X-OriginalArrivalTime: 26 Sep 2010 16:36:44.0030 (UTC) FILETIME=[011DC9E0:01CB5D99] X-RcptDomain: lists.fishpool.fi X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: m.tarenskeen@zonnet.nl Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---1463789311-2014241555-1285519003=:2148 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Sun, 26 Sep 2010, Mark Duckworth wrote: > On 9/26/10 7:27 AM, Martin Tarenskeen wrote: >>=20 >>=20 >> On Sat, 25 Sep 2010, Vincent Rivi=E8re wrote: >>=20 >>> Martin Tarenskeen wrote: >>>> make: ../mintlib/malloc.c:187: __free: Assertion `s =3D=3D r\' failed >>>=20 >>> This is the damn malloc bug. It occurs only inside make. >>> We never managed to reproduce it intentionally, for example after reboo= t. >>> Are you able to reproduce it every time ? That would be a great progres= s. >>=20 >> Yes. It happens always, and always at the same point, and always the sam= e=20 >> message. Can I do something to produce an error report that may give the= =20 >> mintlib developers some more useful info ? >>=20 > Yes, when the malloc bug happens, it always happens at the same point....= but=20 > if you reboot does it still happen and at the exact same spot? Then you= 've=20 > really found something. > It always happens. Rebooting does not make any difference. It happened yesterday, and it will happen tomorrow. And always at the same spot. I will post some info about the version numbers of some relevant=20 components of my build system later. --=20 Martin ---1463789311-2014241555-1285519003=:2148--