BUG in JDEBUG 1.22 (Announce)
> v1.21 contains 1 bugfix
GOOD news: JDEBUG 1.22 is out (2010-11-11, 45 days ago)
BAD news: it still has a BUG:
"DEBUG.TXT" 27'599 2009-05-17 13:46 wrote:
> For a direct memory operand, the offset address of the data is
> specified in the operand. For an indirect memory operand, the offset
> address of the data is calculated at run-time using the contents of
> one or two registers and an optional displacement. In 16bit code, the
> registers can be a base register (BX or BP) or an index register (SI or DI),
> or one of each. The following examples illustrate the differences
> between constant operands, register operands, direct memory
> operands, and indirect memory operands:
> MOV AX,100 ; Moves the value 100 into AX
> MOV AX,BX ; Copies the value in BX to AX
> MOV AX,[100] ; Copies the word at DS:100 to AX
> MOV AL,[BP+2]; Copies the byte at DS:BP+2 to AL
> JMP 100 ; Destination offset is 100
> JMP AX ; Destination offset is the value in AX
> JMP [100] ; Destination offset is the word at DS:100
> JMP [BX] ; Destination offset is the word at DS:BX
> JMP [BX+4] ; Destination offset is the word at DS:BX+4
should be " SS:BP+2 " I ASS'ume. There a few few more things that could be improved in this text, BTW. 
---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***
Complete thread:
- Debug v1.19 - Japheth, 18.10.2010, 08:17
![Open in board view [Board]](img/board_d.gif)
![Open in mix view [Mix]](img/mix_d.gif)
- Debug v1.19 - ecm, 18.10.2010, 19:39
- Debug v1.19 - Japheth, 19.10.2010, 08:33
- Debug v1.19 - ecm, 19.10.2010, 14:23
- Debug v1.19 - Japheth, 19.10.2010, 08:33
- Debug v1.20 - Japheth, 20.10.2010, 09:57
- Debug v1.21 - Japheth, 29.10.2010, 19:13
- BUG in JDEBUG 1.22 - DOS386, 26.12.2010, 08:53
- BUG in JDEBUG 1.22 - Rugxulo, 26.12.2010, 20:58
- BUG in JDEBUG 1.22 - DOS386, 26.12.2010, 08:53
- Debug v1.19 - ecm, 18.10.2010, 19:39
Mix view