go into machine code lazarus / 12-Debugger ---------------------------------------------------------------------- alsor · 2021-03-20 20:42 It's possible to go into binary code in the debugging run? I have in the mind the: cpu state display, machine - assembler code, etc. ---------------------------------------------------------------------- MarkMLl · 2021-03-20 21:14 View -> Debug Windows -> Registers etc. MarkMLl ---------------------------------------------------------------------- Martin_fr · 2021-03-20 21:24 I think keyboard is alt-F7 and alt-F8 But not sure. Tools > Options > Editor > Keymap You can assign keys as you need. https://wiki.lazarus.freepascal.org/IDE_Window:_Assembler https://wiki.lazarus.freepascal.org/IDE_Window:_Registers ---------------------------------------------------------------------- alsor · 2021-03-21 15:39 Something works using alts, but this is still usess, because in the asm code window i cant do any step; F7 returns me to a source code, instead going forth withing this asm instruction... F4 - don't works too Is this debugger... strongly bugged? haha! ---------------------------------------------------------------------- Martin_fr · 2021-03-21 17:17 In the asm window you need to keep using Alt-F7 or Alt-F8. F4 is indeed source code only, and does not work in asm. You can also use the buttons in the asm window. Or in Tools > Option > Editor > Keymap you can find "Step into (context)" and "Step over (context)" and assign F7/F8 to those. Then stepping will be according to which window has focus. This is actually documented on the page I linked https://wiki.lazarus.freepascal.org/IDE_Window:_Assembler#Using_the_sa me_or_different_keys_for_Pascal_and_ASM_stepping Btw Tools > Option > Debugger - there is a setting "AssemblyStyle" in the property grid. Just in case you have preferences But yes, overall the disassembler support is limited. ---------------------------------------------------------------------- Martin_fr · 2021-03-21 17:36 I just tested. It works for me. So I tested trunk. But there is an issue, with the source editor coming to front on each step, and then the asm getting back to front. (Only noticeable if they overlap).