From mint-bounce@lists.fishpool.fi Thu Jun 11 09:48:02 2009 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=nYKXufrwWroXBCKRKgvqKufqrzk6TYsida/eU5BYyM4=; b=EzW6gcfqqGMU39c/Fyjm28dt8S91iC5gRgwKTqx4BiVSn51XhEy94mA3GU3B7sggM6 UwJ/0vNOcJpR7hgIuLTBY3sxbu4MmZhS6KqqbfbCxi14epoDtBclcP2J3teQ2hfPorgF uv9Ol42bK6V9+yfLjCn+yzMDmRSc4DYcrhNWU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=kluMCo2EOQ9YS8L4mLAAN2bHmYJt7pmi0qgj5VVTW6eQF1tg8CJgNmq+TqT1zQ58NJ 8JTyKBR1mDC7QHnp8TcEzBdbuJ/5QI6kzkbHQrCLGq482H8gYVHqoIhrSbd3rJgQOf2V rn8+5OqWMz5JGRy4lsijPYhW2Fumqv5mvoTus= MIME-Version: 1.0 In-Reply-To: <4A310791.2020709@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> Date: Thu, 11 Jun 2009 15:40:59 +0200 Message-ID: Subject: Re: [MiNT] Corruption of high TPA From: Miro Kropacek To: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= Cc: mint Content-Type: multipart/alternative; boundary=001636c59978f7aa7c046c12bd8f X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: miro.kropacek@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: --001636c59978f7aa7c046c12bd8f Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit > > 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. I think there's good chance it is -- I was experiencing that crash exactly as you write -- by calling function for showing error message (i.e. trap #1). -- MiKRO / Mystic Bytes http://mikro.atari.org --001636c59978f7aa7c046c12bd8f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
This is a problem for the early stack. The bug was never triggere= d before, because I guess there was no trap call from the early stack. In m= y 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 crashe= s 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.I think there's good chance it is -- I was experiencing that crash = exactly as you write -- by calling function for showing error message (i.e.= trap #1).

--
MiKRO / Mystic Bytes
http://mikro.atari.org
--001636c59978f7aa7c046c12bd8f--