From mint-bounce@lists.fishpool.fi Wed Feb 18 18:08:18 2009 Message-ID: <499C944D.7090404@freesbee.fr> Date: Thu, 19 Feb 2009 00:05:49 +0100 From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: mint CC: Mark Duckworth Subject: Re: [MiNT] Default Stack Size References: <499C82B4.6060005@atari-source.org> In-Reply-To: <499C82B4.6060005@atari-source.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id n1IN8IJ4001503 Mark Duckworth wrote: > For the time being we are stuck with a one size stack. I was wondering > if anyone has contemplated the idea of setting a default stack size > other than 0 bytes? I think a clean way to fix this problem would be to include a parameter in MINT.CNF called DefaultStackSize. So when the kernel loads an executable with extended MiNT header and the stacksize is set to 0, it will dynamically patch it with the default size. I think it would be easy to get such behavior by making a little patch to Pexec(). Such patch would not break any compatibility. Kernel experts, what do you thing about that ? -- Vincent Rivière