TinySimulator - Invalid memory access at 0x00300000 about mosa-project HOT 5 CLOSED

Yes, I've been chasing this bug as well. I have not been able to narrow down the root cause yet - its deeper than ConsoleManager::Setup(). Any help would be appreciated.

from mosa-project.

I have managed to narrow done the issue to the allocation of objects, took me a while since the record function of the Tiny Simulator slows down simulation by about 1000%.

from mosa-project.

@tgiphil I've found the cause of the issue.

The KernelMemory::AllocateMemory method has been stubbed and the heap was pointing to address 0x300000 which is fine for Bochs but in TinySimulator all memory sections must be explicitly defined and that section of memory is not.

Since we aren't using PageTables by the looks of it, I have just changed the heap to point to 0x2000000 which is the 32MB mark which is the start of Free Memory.

This is only a temporary work around needed until KernelMemory::AllocateMemory has been reimplemented.

from mosa-project.

Good catch on the heap issue.

from mosa-project.

There appears to be in a bug in the PHI placement. Notice that the PHI instruction does not have enough operands. There should be one per incoming block:

System.String Mosa.DeviceSystem.PCI.ClassCodeTable::Lookup(System.Byte) after stage [11] PhiPlacementStage:

Block #29 - Label L_0133
Prev: L_0061, L_006C, L_0077, L_0082, L_008D, L_0098, L_00A3, L_00AE, L_00B6, L_00BE, L_00C6, L_00CE, L_00D6, L_00DE, L_00E6, L_00EE, L_00F6, L_00FE, L_0106, L_012B, L_0123
L_0133 IR.BlockStart
L_0133 IR.Phi V_35 [System.Int32] <= V_35 [System.Int32], V_35 [System.Int32], V_35 [System.Int32], V_35 [System.Int32], V_35 [System.Int32]
L_0133 IR.Phi V_36 [System.String] <= V_36 [System.String], V_36 [System.String], V_36 [System.String], V_36 [System.String], V_36 [System.String]
L_0133 IR.Move V_34 [System.String] <= V_36 [System.String]
L_0134 IR.Return V_34 [System.String] L_7FFFFFFF
L_0134 IR.BlockEnd
Next: L_7FFFFFFF

from mosa-project.