ISO Loader 0.8.x Beta + preview of DreamShell v4.0 RC 5

[VeraBecker]

(16.08.2023 08:26)SWAT писал(а):  @VeraBecker
After launch iso loader firmware, what in the memory doesn't matter, game uses it as they needed and all of them.
The memory allocation doesn't shared between DS and Game because DC doesn't have an OS that always works.
Only ISO loader firmware can use the same memory as game through special mode for the Heap param named as KATANA heap.
But the observation is good, perhaps the state of the hardware is different after some manipulations.

malloc_stats just print debug info to dev console. It's disabled for DS in general, because it's needed for debug only.
You look at the Core level, but all these problems should be solved in the iso loader firmware I think.
It is necessary to set the state of the hardware more correctly before launching the game binary, not the loader.

Thanks, so the behavior is strange, it happened to me that it left a pointer to an address in Windows applications, and since it didn't leave it in NULL, depending on what I did, the program sometimes crashed, that's why I thought it was some object that it starts in the IsoLoader and that it stays in memory, anyway I'm going to try to check it over the weekend.