TOS 1.x memory pool management

[Cyprian]

looking for any info how TOS 1.x manages the memory pool.

I guess there is a table of used memory blocks with their application ID.

[ParanoidLittleMan]

Did not see any detailed description how it exactly works. There is table for sure, and probably instead app. ID   basepage address is what identifies app.  I did some hack with it, to make lowering RAMtop without reset, what consists mostly from seeking values in area at $800 which match criteria: memtop-basepageadr = free RAM (what is all free RAM at APP start by TOS) .

In Atari ProfiBuch stays that TOS can handle limited count of memory blocks, and that's normal. Table space is limited.

What I know is that whole system works good enough reliable in normal usage. But there are some flaws - like every new APP start will be placed 14 bytes higher than previous. The reason is probably that whole thing is complex, and PRG starts not on same adr. as TOS, because PRG needs AES, so more RAM is allocated for system in that case. But when start TOS after PRG it will be placed on same high adr. (+14) as PRG started.

I recommend using Steem Debugger and tracing it ?

[Cyprian]

thanks for explanation,

I have a memory dump and I have to track every memory block used by an application

I'll try to debug Malloc

[Cyprian]

I've found a clue:

1) FOLDRXXX increases entries in the TOS pool. There is an opensource version done my MFro: https://github.com/mfro0/foldrxxx

2) osmem.c from EmuTOS