From mint-bounce@lists.fishpool.fi Thu Jun 11 11:54:53 2009 X-Spam-Status: No, hits=-1.0 required=5.0 X-Spam-Report: SA TESTS -1.1 BAYES_05 BODY: Bayesian spam probability is 1 to 5% [score: 0.0375] 0.1 AWL AWL: From: address is in the auto white-list Mime-Version: 1.0 (Apple Message framework v753.1) In-Reply-To: <4A311332.90806@freesbee.fr> References: <4A2ED03D.1090600@freesbee.fr> <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; delsp=yes; format=flowed Message-Id: <40E5F01B-BEA7-41BD-B9D2-4FAC890CBA0E@bassment.nu> From: Maurits van de Kamp Subject: Re: [MiNT] Corruption of high TPA Date: Thu, 11 Jun 2009 17:50:04 +0200 To: mint@fishpool.com X-Mailer: Apple Mail (2.753.1) X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: maurits@bassment.nu Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id n5BFsqr8003528 I tried tst.tos on my STe (4MB, MiNT 1.15) and my TT (4+64MB, MiNT 1.16.3a). It works on the STe (with memory protection, at least I think it's switched on, MiNT is NOT named mintnp.prg) :) Indeed, no fastram. On the TT it only works without memory protection; with memory protection it gives the following memory violation: Type: Free Addr: 01B9201A PC: 012BA37E BP: 01A90000 OS: FF82A27E I should add that I normally run my TT with memory protection off, and that now I swithched it on, the Thing desktop had crashed first after which I launched Toswin straight from the XaAES menu. Dunno if this is the most reliable setup. ;) Maurits. On Jun 11, 2009, at 4:22 PM, 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. > >> Did you enable the NEW_SYSCALL stuff in the kernel and the bug >> disappeared ?? > > No, I'm not familiar with the kernel, I didn't try to recompile it. > NEW_SYSCALL looks better, but I don't know if it works. > > -- > Vincent Rivière > move.l 4(sp),a0 | get basepage > move.l 4(a0),d0 | get _base->p_hitpa > and.l #0xfffffffc,d0 | align on lower 4 bytes > > | sub.l #0,d0 | Bus Error before Hello > | sub.l #28,d0 | Bus Error before Hello > | sub.l #32,d0 | Bus Error after Hello > | sub.l #36,d0 | No Bus Error > > move.l d0,sp | this is the new stack > > pea msg > move.w #9,-(sp) | Cconws() > trap #1 > addq.l #6,sp > > move.w #8,-(sp) | Cnecin() > trap #1 > addq.l #2,sp > > clr.w -(sp) | Pterm0() > trap #1 > > msg: .asciz "Hello!\r\n"