diff options
author | Kartik Agaram <vc@akkartik.com> | 2020-02-05 10:33:28 -0800 |
---|---|---|
committer | Kartik Agaram <vc@akkartik.com> | 2020-02-05 14:57:52 -0800 |
commit | 9ee351f37fbf78aa408f60c0d2c7ec49e625f109 (patch) | |
tree | ed55ef4c9cfcbedefda64767164855b576748c75 /014indirect_addressing.cc | |
parent | b9d666eff51659a62dab7b746e5ae40431127e9b (diff) | |
download | mu-9ee351f37fbf78aa408f60c0d2c7ec49e625f109.tar.gz |
5983 - fix an emulator bounds-check bug
It was possible for an instruction to write out of bounds of the memory data structure. Most of the time this worked fine. However if the block ever got resized and moved the out-of-bounds bytes no longer went along.
Diffstat (limited to '014indirect_addressing.cc')
-rw-r--r-- | 014indirect_addressing.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/014indirect_addressing.cc b/014indirect_addressing.cc index 9c50c129..19d4d509 100644 --- a/014indirect_addressing.cc +++ b/014indirect_addressing.cc @@ -818,7 +818,7 @@ case 0x8f: { // pop stack into r/m32 case 0: { trace(Callstack_depth+1, "run") << "pop into r/m32" << end(); int32_t* dest = effective_address(modrm); - *dest = pop(); + *dest = pop(); // Write multiple elements of vector<uint8_t> at once. Assumes sizeof(int) == 4 on the host as well. break; } } |