4 ms·

Are you running on QEMU? How do you make t stop after every step? And why did t did not stop at mov bp,sp for you? I can't get tracing to work at https://copy.

by distcs 4y ago

Are you running on QEMU? How do you make t stop after every step? And why did t did not stop at mov bp,sp for you? I can't get tracing to work at https://copy.sh/v86/?profile=msdos https://copy.sh/v86/?profile=msdos Modified OP's code to add more steps to see some stepping through but T makes the program run all the way to termination - https://i.imgur.com/hiYeC2x.png https://i.imgur.com/hiYeC2x.png

blueflow 4y ago
I think the CPU emulator of that website is just buggy
- distcs 4y ago
  Do you know why in nathell's link the first t does not stop at mov bp,sp? It stops at other lines but not that one. Could that be a buggy emulator too?
  - blueflow 4y ago
    I'll try it later on a physical machine.
  - nathell 4y ago
    I think the UI is just confusing. T means „execute the instruction at CS:IP, advance IP and display the next instruction to execute”. So the first T executes the first instruction but displays the second.
nathell 4y ago
I tried in DOSBox. It was years ago, so I don’t remember all the details. Maybe it’s a DOSBox issue that has since been fixed!
nathell 4y ago
Looks like v86 doesn’t implement the INT 3 (0xCC) opcode, which the debuggers use to step through: https://github.com/copy/v86/discussions/653 https://github.com/copy/v86/discussions/653