Project

General

Profile

Emulator Issues #10961

[Qt] Debugger has usability issues

Added by leoetlino over 2 years ago. Updated over 2 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
Yes
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:
5.0-7437

Description

  • When a code breakpoint is hit, the debugger code pane does not refresh the code view to show the instruction. Actually, the UI never updates at all -- the play button still reads "Pause" and not "Play".

  • Boot to Pause does not work.

  • Resizing the debugger side panel (or any of the small panels) is really, really slow and results in significant CPU usage.

  • For consistency with DolphinWX, the debugger panes should probably default to being shown on the left side.

History

#1 Updated by leoetlino over 2 years ago

Scrolling in the code pane also does not seem to work properly. Doing it causes the UI to eat a full core but nothing is actually scrolled.

#2 Updated by leoetlino over 2 years ago

Looks like the problem for Boot to Pause is that the setting is never getting loaded or saved. It actually works fine if you manually enable it.

Also, I cannot get the first issue to happen consistently, so it may be some kind of race condition :/

#3 Updated by leoetlino over 2 years ago

Since the scrolling issue is surprisingly not easy to reproduce, I'll provide some steps:

  1. Launch DolphinQt2 and enable the debug UI.
  2. Show the code pane.
  3. Launch a game (for example The Legend of Zelda: Twilight Princess)
  4. Pause emulation and set a breakpoint on the next instruction (PC + 4)
  5. Resume emulation

Expected results:

Emulation should immediately pause again. It should be possible to scroll in the code pane.

What happens instead

Emulation pauses (as expected), but scrolling just causes the UI to use 100% CPU time without actually scrolling.

#4 Updated by leoetlino over 2 years ago

  • Fixed in set to 5.0-7437
  • Status changed from Accepted to Fixed

All issues are now fixed in 5.0-7437

Also available in: Atom PDF