From mint-bounce@lists.fishpool.fi  Tue Jan 22 17:32:45 2008
X-Original-To: fnaumann@mail.boerde.de
Delivered-To: fnaumann@mail.boerde.de
X-ME-UUID: 20080107185319666.A2B37700009A@mwinf2327.orange.fr
Date: Mon, 7 Jan 2008 19:53:18 +0100
From: Patrice Mandin <mandin.patrice@wanadoo.fr>
To: mint@lists.fishpool.fi
Subject: Re: [MiNT] gcc 4.2.2 compile error
Message-Id: <20080107195318.62b9ec54.mandin.patrice@wanadoo.fr>
In-Reply-To: <47825C1D.9000306@freesbee.fr>
References: <c6533ef60801011247x7114e5f8xfce6ccd1ad10272@mail.gmail.com>
	<200801032257.16394.oak@helsinkinet.fi>
	<c6533ef60801040104n373a0497l9d9afc37cd426957@mail.gmail.com>
	<200801042028.18829.oak@helsinkinet.fi>
	<c6533ef60801070120q322dc5dcoc843853bee318799@mail.gmail.com>
	<47825C1D.9000306@freesbee.fr>
Organization: Chez moi
X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-To: mint-bounce@lists.fishpool.fi
X-original-sender: mandin.patrice@wanadoo.fr
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>
X-Virus-Scanned: by amavisd-new at relay.boerde.de
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de
X-Spam-Status: No, hits=-1.0 tagged_above=-50.5 required=7.0 tests=BAYES_00
X-Spam-Level: 
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by freemint id m0MGP1dZ004618
Status: 
X-Status: 
X-Keywords:                   

Le Mon, 07 Jan 2008 18:06:37 +0100
Vincent Rivière <vincent.riviere@freesbee.fr> a écrit:

> However it would be nice if FreeMiNT could do some stack checking...
> For  example, on task switching, or on system calls, it could check
> that the  stack pointer is greater than the end of the data segment.

Or make the kernel to have a proper virtual adress space for each
process, and put the stack at the end of it :). And when there is a bus
error on stack, add more memory pages below it.

-- 
Patrice Mandin
WWW: http://pmandin.atari.org/
Programmeur Linux, Atari
Spécialité: Développement, jeux


