From mint-bounce@lists.fishpool.fi  Mon Apr 27 14:14:43 2009
Date: Mon, 27 Apr 2009 14:08:51 -0400 (EDT)
From: Keith Scroggins <kws@radix.net>
To: Miro Kropacek <miro.kropacek@gmail.com>
cc: mint@fishpool.com
Subject: Re: [MiNT] Possible MintLib FastRAM bug in TOS/MagiC? (Or My Own 
 Error...)
In-Reply-To: <c6533ef60904271024w33e416f3gf74db208d7903380@mail.gmail.com>
Message-ID: <Pine.GSO.4.63.0904271337060.16630@saltmine.radix.net>
References: <Pine.GSO.4.63.0904271255520.16630@saltmine.radix.net>
 <c6533ef60904271024w33e416f3gf74db208d7903380@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; 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: kws@radix.net
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>

Hello Miro,

Thanks for the reply.

>> Did any of this make sense, need more info?
>
> Probably not much of help but -- are you aware of the fact you can't call
> mxalloc in the TOS with that MiNT flag (bit 3) set? Because if you do, the
> call will fail -- I remember to fail here when I was doing mxplay. Maybe
> some of your / SDL code uses this with MiNT flag set.

This is the -a flag (set the fast ram allocation flag)?  Removing that bit 
should help, or most likely will not make a difference? (I will try it 
when I get home, along with GCC 4.4.0).

I do know the out of memory is happening in a calloc call, which I am 
guessing (and I could be totally wrong) is being converted to a mxalloc in 
TOS.  This call does work when less memory is needed/used.

Keith