search

Trinity-11 / FoenixIDE

Development and Debugging Suite for the C256 Foenix Family of Computers
GNU General Public License v3.0
48 stars 14 forks source link

Fix problem where new breakpoints don't "take effect" until after you pause the debugger #60

Closed clandrew closed 1 month ago

clandrew commented 1 month ago

I saw this misbehavior

  1. Be running some program
  2. Open the "Breakpoints" menu
  3. Type in a breakpoint address that you know is being executed
  4. Close the menu

Expected: Program immediately breaks Actual: Program doesn't break. Reason: new breakpoints don't "take effect" until you pause execution

Proposed fix: make the "Breakpoints" menu pause the debugger for you. This is consistent with other debuggers I've used in the past. To make this effective, the dialog has to be modal, so the fix includes that.

I vetted the idea for fixing this with another user xDraconian in the Discord channel.