From mint-bounce@lists.fishpool.fi  Thu Jun 11 10:45:05 2009
X-Virus-Scanned: amavisd-new at demon.co.uk
Subject: Re: [MiNT] Corruption of high TPA
From: Alan Hourihane <alanh@fairlite.co.uk>
To: Vincent =?ISO-8859-1?Q?Rivi=E8re?= <vincent.riviere@freesbee.fr>
Cc: mint <mint@fishpool.com>
In-Reply-To: <4A311332.90806@freesbee.fr>
References: <4A2ED03D.1090600@freesbee.fr>
	 <alpine.BSF.2.00.0906101033540.29737@antyk.ibi.uw.edu.pl>
	 <4A2F7B9F.3010100@freesbee.fr>  <4A30FE49.3050404@freesbee.fr>
	 <1244725809.15756.100.camel@jetpack.demon.co.uk>
	 <4A310791.2020709@freesbee.fr>
	 <1244728568.15756.106.camel@jetpack.demon.co.uk>
	 <4A311332.90806@freesbee.fr>
Content-Type: text/plain; charset="ISO-8859-1"
Date: Thu, 11 Jun 2009 15:41:18 +0100
Message-Id: <1244731278.15756.109.camel@jetpack.demon.co.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.24.5 
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-to: mint-bounce@lists.fishpool.fi
X-original-sender: alanh@fairlite.co.uk
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id n5BEj557003656

On Thu, 2009-06-11 at 16:22 +0200, Vincent Rivière wrote:
> Alan Hourihane wrote:
> > I get a little uneasy about adding patches to mintlib when we can't
> > reproduce the bug on more than one system.
> 
> You're right.
> 
> > Has anyone else reproduced
> > this without Aranym/EmuTOS ?
> 
> First, the test must be made with a problematic executable. Any program 
> compiled with the current CVS MiNTLib is affected. The tiny program 
> tst.tos attached to this email does not use the MiNTLib but is affected 
> in the very same way.
> 
> The crash occurs only when the OS loads the program at some memory 
> location where there is an invalid read address just after. For example, 
> at the end of the FastRam (like EmuTOS). I guess that with the right 
> memory protection parameters, the space just after the TPA is marked as 
> unreadable, it is probably what happens on my setup.

This is the same tst.s I compiled before and it works here. Are there
any configuration settings in mint.cnf that sets any TPA related changes
in your setup ?

Alan.