Re: load_region() problem :(

[Torsten Scherer (Schiller) <itschere@TechFak.Uni-Bielefeld.DE>]

 Kay writes:

> (...) In the latter case fragmentation might be caused by TCP sockets. (...)

 No no no! If I was misunderstood at this point: The problem has got nothing
to do with MiNTNet. (In fact memory may perhaps get fragmented by it but that
is not at all my concern (at least not now and here))

 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.

ciao,
TeSche