You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some of the tests that I've written I had used static strings to test out some functions that needed to have write access to those strings (this was to temporarily terminate a filepath, excluding it's leafname). in the emulator these tests worked fine, but on real hardware they don't. it makes sense that the tests failed on real hardware, as the attempt to temporarily terminate the filepath should have failed. My tests were easily fixed by copying those strings into the heap before use.
From my observations it therefore seems that the emulator is allowing memory writes to the ROM memory space
The text was updated successfully, but these errors were encountered:
Interesting gotcha...
In some of the tests that I've written I had used static strings to test out some functions that needed to have write access to those strings (this was to temporarily terminate a filepath, excluding it's leafname). in the emulator these tests worked fine, but on real hardware they don't. it makes sense that the tests failed on real hardware, as the attempt to temporarily terminate the filepath should have failed. My tests were easily fixed by copying those strings into the heap before use.
From my observations it therefore seems that the emulator is allowing memory writes to the ROM memory space
The text was updated successfully, but these errors were encountered: