View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0032654||Lazarus||IDE||public||2017-11-07 04:50||2019-01-10 01:04|
|Reporter||J. Gareth Moreton||Assigned To||Martin Friebe|
|Platform||Win64||OS||Windows 7 (64-bit)||OS Version||Enterprise|
|Product Version||1.6.4||Product Build||r54278, x86_64-win64-win32/win64|
|Target Version||Fixed in Version|
|Summary||0032654: Register Debug Window keeps recreating the list upon Step Over / Step Into|
|Description||There is a very annoying issue with Lazarus in that the Debug Window that displays Registers (Ctrl+Alt+R) under Windows 64-bit (and 32-bit too, I believe). When you step through your program, the list is refreshed every time. The problem with this is that it scrolls the window back to the top, which is irritating if you want to only look at, say, AX instead of the full 64-bit RAX (of which the upper bits may contain garbage data) and also reverts the display format for a register back to Default, which is awkward when you want to evaluate the integer or raw memory on an XMM register.|
|Steps To Reproduce||Compile and run any program, and place a breakpoint anywhere in the source code that the execution will reach (it can either be Pascal or Assembler code) - when the debugger breaks out, view the Registers window, scroll down and/or change the Format of fields of your choice, then press F7 or F8 to step once through the program. Observe the Register window completely clear and re-create the list items, with the scrolling right back at the top and all the value fields reverting to the default format.|
|Additional Information||Ideally, the Lazarus IDE should only change the Value fields, not re-create the entire list, because the actual registers present should never change.|
|Tags||No tags attached.|
|Fixed in Revision|
The scroll part is solved in revision 60049.
Normally the display is cleared while the debugger is running (that includes stepping, as step-over could step over a long running procedure).
Note, that (in future / depending on the backend) the list of shown registers can change.
If the stackframe is changed, not all registers' values can be retrieved for calling frames. GDB shows (probably) valued of the top frame for those. Lldb does omit them from the list.
The display format (hex/dec/oct) is still reset on each step.
This requires rework in the backend code.