diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2015-07-17 12:51:32 -0700 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2015-07-17 12:58:37 -0700 |
commit | 32cd40ec3c9dad33738caf6f55fb742a316bd5be (patch) | |
tree | c6612fefc35741b43e1058826445d2913e94b3ba /051scenario_test.mu | |
parent | fe9e53ed19f84a1771d56bfa0cf7d1d017e07559 (diff) | |
download | mu-32cd40ec3c9dad33738caf6f55fb742a316bd5be.tar.gz |
1799 - continue to debug memory corruption of 1795
Things I figured out: - 'row' in render-screen doesn't perfectly track cursor-row in screen - proximal cause was forgetting to add left:number to stop-printing - trying to print to screen outside bounds was silently succeeding and corrupting simulated memory - if we silently ignore prints outside bounds things are fine But why are prints outside screen bounds working? We should be accessing screen data using 'index', and that's checking its bounds.
Diffstat (limited to '051scenario_test.mu')
0 files changed, 0 insertions, 0 deletions