From mint-bounce@lists.fishpool.fi Sun Sep 26 16:58:32 2010 X-SourceIP: 77.251.205.36 Message-ID: <4C9FB379.2040905@chello.nl> Date: Sun, 26 Sep 2010 22:56:25 +0200 From: Henk Robbers User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] compile problem References: <4C9E58F4.1080604@freesbee.fr> <4C9F55EF.1000004@freesbee.fr> <4C9FAF71.90408@chello.nl> In-Reply-To: <4C9FAF71.90408@chello.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Cloudmark-Analysis: v=1.1 cv=BBXmjR/jrMMj1wHBsuD7Cdv69cLzNztNz9uR8CXiauo= c=1 sm=0 a=8nJEP1OIZ-IA:10 a=HpkHhv1iAAAA:20 a=JxdZti4tAAAA:8 a=k6pALyOojmmIYGHRrnkA:9 a=sL7F6oykaoKhm7WzQIfTe1F6nooA:4 a=wPNLvfGTeEIA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: h.robbers@chello.nl Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: And if you then insert some debug code, the whole memory image slightly shifts and the bug does not occur anymore. And so the bug has never been solved. It could also be a memory corruption that has nothing to do with malloc itself, but shifts in and out of harmfullness when internal distances in a program change. It could be a violation of the space of a allocated area. Sometimes it corrupts a area already in use, sometimes it corrupts a free area and then doesnt harm. -- Groeten; Regards. Henk Robbers. http://members.chello.nl/h.robbers Interactive disassembler: TT-Digger; http://digger.atari.org A Home Cooked C compiler: AHCC; http://ahcc.atari.org