From mint-bounce@lists.fishpool.fi Sun Apr 27 12:32:45 2008 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:organization:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=wer1pv2fgBIjzdsV9Yop+rDxnyJhKGM1S8TYFmykSYs=; b=wLoh1UCVIw+vZcg/n/kYAl6YL41mFLem70tGJ3SFS/fvnGwcVXriXR54y6h/k7TapAc80jq7+xf+TP8q8PQ20e/pdN7Ae+lyPcY5+6CVFV3p2WkssLSA1jGxJGDtYYtY+/5V29byE19qLo3ayXB3rh32+1aqX6UCN4NM9nQLM6U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=nNXXibmT1c9wAaokeuWCmB9QS3MTG6C56UvFWlD6UIxr5ww85BFx/2onJ/UeuIlXYP6SkIU4K8qyioU1zCL8AunhyBSvJbqiHWkls1591c0wQeL/rr4R0H1qzS1otnhjfAoJk9WIaOUM+wMNwsybc7ks/DWUldHMr/yzgTNume8= Message-ID: <4814A8A4.7090704@gmail.com> Date: Sun, 27 Apr 2008 18:24:04 +0200 From: Miro Kropacek Organization: Mystic Bytes User-Agent: Thunderbird 2.0.0.12 (X11/20080227) MIME-Version: 1.0 To: Frank Naumann CC: mint Subject: Re: [MiNT] mintlib release References: <1209150190.9724.530.camel@jetpack.demon.co.uk> <48144B02.60400@freesbee.fr> <48146E22.2060606@freesbee.fr> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: > With preliminary stack you mean the stack before the Mshrink()? This > happened under FreeMiNT? How can this yes and yes :) > reproduced? Inside mint.cnf, was there TPA_INITIALMEM set and to which > value (and how many RAM does the machine have). > see my previous mail. the way to reproduce isn't easy -- the basic rule is to have less TPA than needed... you can for example try to set big stacks with "stack --fix" under this environment for some binaries but it's always about luck -- remember, if my theory is right, it's everything about one byte beyond the memory area for that process and this byte can or cannot make some troubles. -- MiKRO / Mystic Bytes http://mikro.atari.org