Confusing DEBUG - EDIT (Miscellaneous)
> > - read the byte at CS:E/IP-1
> > - restore its BPs
> > - if the byte it has read is 0CCh AND entry into Debug was through
> > interrupt 3, then it again reads the byte at CS:E/IP-1.
>
> Fits my description up to here.
I saw - and still see - some differences, but this is probably off-topic.
However, what's on-topic is that I'm unable to see why DEBUG is supposed to be "confused". I also don't agree that it "incorrectly decrements (E)IP". If the conditions described above are met then (E)IP has to be decremented, it doesn't matter if the INT 3 was truly executed or if it was "faked".
---
MS-DOS forever!
Complete thread:
- Confusing DEBUG - ecm, 16.08.2010, 04:11 (Miscellaneous)
![Open in board view [Board]](img/board_d.gif)
![Open in mix view [Mix]](img/mix_d.gif)
- Confusing DEBUG - Japheth, 19.08.2010, 00:52
- Confusing DEBUG - EDIT - ecm, 19.08.2010, 01:19
- Confusing DEBUG - EDIT - Japheth, 19.08.2010, 10:17
- Confusing DEBUG - ecm, 19.08.2010, 11:00
- Confusing DEBUG - EDIT - Japheth, 19.08.2010, 10:17
- Confusing DEBUG - EDIT - ecm, 19.08.2010, 01:19
- Confusing DEBUG - Japheth, 19.08.2010, 00:52
Mix view