When the debugger stops at a breakpoint or gets paused, the register dialog is populated with registers supplied by the back end. The order of the registers typically doesn't change (depending on the back end I assume, I am interested in fpdebug specifically). If one changes the current call stack frame to a different frame, typically fewer registers are available and the displayed register list is shorter. If one then moves back to the top call frame (with all registers available), the order of the registers is affected. The registers previously displayed stays at the top of the list, while newer (not previously available) registers are added to the bottom of the list.
For an example refer to the attachments, which shows registers views for 1) the top level frame, 2) the next frame, 3) back to the top frame. My expectation is that the register order should be as the back end supplied them unless the user selected a sort option.
What is the general opinion on this, is this the desired/expected behaviour? I want to change this, but there is quite a bit of code to implement the current behaviour. I do not want to change this if there are reasons that I am unaware of.
Recent
