Re: load_region() problem :(

[lom@tc.multi.se (Mats Loman)]

> It *can* happen with all -mbaserel programs if there's only very few
>TT-RAM left. I've reproduced it with a program which does nothing but
>Malloc() and stay idle. Note: THIS program wasn't -mbaserel! But as soon
>as TT-RAM was low (not zero!!!) programs like `ls' or `ps' failed. These
>Programs were -mbaserel and prepared to run in TT-RAM. I didn't check what
>happens if I reset them to ST-RAM, but I did check they run perfectly well
>if I reset the shared text bit in prgflags.
>
> This can't obviously be called a fix... :(
>
> Would there be interest if I post a small package to reproduce it? I
>don't actually have it but it really isn't very much. As I said: Just
>take something which Malloc()s and stays idle. I use a small tool which
>Malloc()s all memory it can get to print out *each* free block, not just
>the biggest one. If there's only, say, 64k left, try running any -mbaserel
>program -> Killed.
>
I have some strange problems when loading emacs and gcc (all versions). 
Sometimes they crashes when loading, maybe that is a clue! 

I can compile a bunch of files and then gcc crashes with and illegal 
instruction or more often memory violation (I have memory protection on). 
When I restart the compilation most of the times it works fine but sometimes 
I have to try more than one time. Emacs crashes allso with a memory 
violation. The memory allways points to not owned but free memory.  I would 
say that this behaviur started in MiNT 1.10hx (x<6). 

My system has 16Mb TT-Ram and 4Mb ST-Ram and a graphics card.
----------------------------------
Mats Loman -- <lom@tc.multi.se>
----------------------------------


--

-----------------------------
Mats Loman <lom@tc.multi.se>
-----------------------------