diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2021-04-28 22:03:58 -0700 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2021-04-28 22:03:58 -0700 |
| commit | dcb6a21a911d61c51d1f54c357b5c6fcb01dd7cc (patch) | |
| tree | 91be83a868bd8e04f3eba2b4ec7889b1b72f5cb4 /archive/1.vm/build3 | |
| parent | 7fa356abef56cc72e730f7bc0648c3968a3464d6 (diff) | |
| download | mu-dcb6a21a911d61c51d1f54c357b5c6fcb01dd7cc.tar.gz | |
bugfix: initialize gap buffers before using them
I keep running into one hole in Mu's memory-safety since dropping the Linux dependency: null pointers no longer error when dereferenced. Here the problem manifests as aliasing: lots of gap buffers share the same exact data near address 0, because it was never initialized.
Diffstat (limited to 'archive/1.vm/build3')
0 files changed, 0 insertions, 0 deletions