From mint-bounce@lists.fishpool.fi Thu Jun 11 09:41:40 2009 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:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=GjS88xuIgklW5JC0igHrN9X29ALEOnwvkpikvZEBPQs=; b=R0FJ4IqB2f1k3msc5qKayZuGy4Vi+YO7JRvci+lwo49deq2RSJ5wS0In7pKdv9BV4O zW3rkmW0jkGhiM0yNQXUYgs8pVWmUBVF6UNJ6fGELJ35YVCOsqniwHK5CzvGkJByXmPD mZ1wQIDuJJ2jbO7/5LTx8hr3uv2E78hmyErK8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=av2g7pUW9bXZxwwZDu3SZpYXNOHPMw+2aS8NSXKJCgupWwnl60zGi2w6P/pej/MwhR eUzbgTYEaZUfCqRYDCCfHnEzCR3ymVxsA5vuAPTtZB59JYU49uEHZIxddfmhYOMux+bo 7xx60c/S1Q38btTP+NG1y2qa1eLuIgX68qdDE= Message-ID: <4A310791.2020709@freesbee.fr> Date: Thu, 11 Jun 2009 15:33:05 +0200 From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: mint CC: Miro Kropacek Subject: Re: [MiNT] Corruption of high TPA References: <4A2ED03D.1090600@freesbee.fr> <4A2F7B9F.3010100@freesbee.fr> <4A30FE49.3050404@freesbee.fr> <1244725809.15756.100.camel@jetpack.demon.co.uk> In-Reply-To: <1244725809.15756.100.camel@jetpack.demon.co.uk> 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: Alan Hourihane wrote: > I'm pretty sure I have memory protection enabled here when I did the > test. Why don't I see the problem ?? I don't understand exactly when it becomes visible, because I have very limited knowledge about memory protection settings. The only concrete fact is I have an ARAnyM disk image where the tst.tos binary crashes. This is a problem for the early stack. The bug was never triggered before, because I guess there was no trap call from the early stack. In my latest patch for the startup code, I added a Ssystem() call very early on the early stack, so any programs built with the current CVS MiNTLib crashes before main() on systems (like mine) where the bug is visible. MiKRO, that reminds me the strange problems you experienced when the system is going out of memory. I don't know if it is related or not. -- Vincent Rivière