Development of Tlsfmem as Memtlsf Allowed by Chris Hodge

[ChaosLord]

TLSFmem Forever!

I haven't detected any bugs yet.

Anxiously awaiting the release of TLSFMungWall  :idea:

[ChaosLord]

f the mungwall not work, doesnt matter, because mugwall is not usefull for developing today, because it tracks not poolmem.

True!

a tool that do that and more is wipeout.it is opensource and with that tlsfmem that work.

I never knew about this!  It sounds awesome!  Why nobody tells me these things?!?! :-D

[ChaosLord]

it is important that the developers tools work 100% with memtlsf.

Yes!

memfree on old AOS memallocater is very slow,

Very true!

but of course i use a modern graphical assembler ide where i can click on a jsr label and the editor jump to the label.this is important to navigate in unknwon programs that do many nestet jumps

Amiblitz Assembler sounds awesome!

[ChaosLord]

That is awesome!  Back when Blitz Basic first came out (1988?) I begged them for that feature!  But they would not do it for me.  :-(   I told them I would pay them $200.00 for that feature so I could just use Blitz Basic as my Assembler.  Oh well... 20 years waiting is better than never. :-)

[ChaosLord]

As u know TLSFmem and MuGuardianAngel don't get along with each other.

Some years back I was discussing this with THOR and to make a long story short: MuGuardianAngel needs to be rewritten to "work the way TLSFmem works".    Currently MuGuardianAngel relies on deeply intricate inner workings of the plain old ancient AmigaOS memory management system.

It really sux that I have to keep nuking TLSFmem and rebooting my machine every time I want to run MuGuardianAngel.

In a perfect world I could run both MuGuardianAngel and TLSFmem all the time on my dev machine and speed up my bug-catching and bug-destroying.

Thor will not rewrite MuGuardianAngel.  So basically we need Bernd or we're all dead.

Help me Berndi-wan Kenobi, ur my only hope.  My only hope.