FpDebug, small x86 disassembler bug

[mika]

Code: Pascal  [Select][+][-]

1. program testdbg18;
2. {$apptype console}
3. {$mode objfpc}{$h+}
4.  
5. uses FpDbgDisasX86, FpDbgClasses, FpDbgUtil;
6.  
7. const  testCode : shortstring = #$a3#$1a#$00#$00#$00; {mov [$0000001a],eax}
8.  
9. var    p : pointer  ;
10.        codeBytes, asmInstr : string;
11.        pr : TDbgProcess;
12.        de : TX86AsmDecoder;
13.  
14. begin
15.      pr:= TDbgProcess.create(dm32);
16.      de := TX86AsmDecoder.create( pr );
17.      p:=@testCode[1];
18.      de.Disassemble(p, codeBytes, asmInstr );
19.      writeln;
20.      writeln( codeBytes:20,'    ', asmInstr);
21.      readln;
22. end.

output
          A31A000000    mov dword ptr [$0000001A],al

output should be
          A31A000000    mov [$0000001A],eax

file fpdbgdisasx86.pas

Code: Pascal  [Select][+][-]

1.       $A3: begin
2.         SetOpcode(OPmov);
3.         AddOv;
4.         AddReg(regGeneral, os8, REG_A);
5.  

fix

Code: Pascal  [Select][+][-]

1.       $A3: begin
2.         SetOpcode(OPmov);
3.         AddOv;
4.         AddReg(regGeneral, OperandSize, REG_A);
5.  

[PascalDragon]

Please report on the bug tracker.

[mika]

Please report on the bug tracker.

Not registered there. Not going to report.
Your suggestion i will take as a hint to not report bugs in forum.
But if some one is going to investigate this, then look at lds,les,.. instructions with operand and address size modifiers.

[Martin_fr]

Please report on the bug tracker.

Not registered there. Not going to report.
Your suggestion i will take as a hint to not report bugs in forum.
But if some one is going to investigate this, then look at lds,les,.. instructions with operand and address size modifiers.

You can mention bugs here. Sometimes they will be spotted. And then it's a question if they will be remembered.
For now, I noted this one. Hopefully it wont fall through the cracks....

The bug tracker makes sure it will be remembered.

[Martin_fr]

Fixed

[Bogen85]

Fixed

Fixed, as in, fixed in the source code? If so, what is the issue tracker number for this?

I did not know this existed for FPC (disassembly functions), though due to this Topic I now see that it is the Lazarus sources.

[Martin_fr]

Fixed

Fixed, as in, fixed in the source code? If so, what is the issue tracker number for this?

The commit is 4c879cc73cc403526099b3eadde64c03c9a82f31

There is no bug tracker id, since - as you may have read - the reporter did not want to create an account to the tracker.

Which means, it is lucky I got time now. Otherwise it might easily have been forgotten.
- "Time" just doesn't mean the 30 seconds to change one word, and commit it.
- "Time" means everything from checking that this is currently wrong, and that the suggest disassemble is the correct one. We are all humans, the reporter could have mis-reported too. Then checking that the changed line returns the new desired value. Checking desired, current, and fixed results for other op-sizes (which would be expected to exist). So "Time" amounts. And had I been in the middle of something else, I might not have interrupted that (even if that be a project taking a few month).

I did not know this existed for FPC (disassembly functions), though due to this Topic I now see that it is the Lazarus sources.

They exist in Lazarus => FpDebug. Since the debugger should be able to display disassembly.

[Bogen85]

The commit is 4c879cc73cc403526099b3eadde64c03c9a82f31

There is no bug tracker id, since - as you may have read - the reporter did not want to create an account to the tracker.

Which means, it is lucky I got time now. Otherwise it might easily have been forgotten.

Got it!

I understand.

They exist in Lazarus => FpDebug. Since the debugger should be able to display disassembly.

Thanks!

Per the code in the reporter's example this will be useful to me in non-gui programs.

[Martin_fr]

Btw, if anyone has spare time....

But if some one is going to investigate this, then look at lds,les,.. instructions with operand and address size modifiers.

This indicates that there may or may not be other similar cases.

But I don't have time to verify this currently.