There are a couple more issues with the N++ debugger:
- The debugger will not connect until the following command from the run menu item is executed:
- Once the breakpoint pane is hidden, there doesn't appear to be any way of unhiding it until the next N++ restart.
- N++ 6.9.2 can produce an "index out of bounds (0)" when using the add breakpoint button. When several breakpoints are added with the button, it can happen that the first is deleted on the next press of the button. Doesn't happen when R-click add breakpoint, but symptomatic when N++ loses connection with DBGp.
- The debugger is liable to crash N++ (Application Hang) but it is difficult to pinpoint any particular causal event:
notepad++.exe
6.9.2.0
43bc
01d2052f64ac1dca
28
C:\Program Files (x86)\Notepad++\notepad++.exe
b6ee40d4-71a5-11e6-ba33-bc5ff478687a
430072006F00730073002D00740068007200650061006400000044006500610064006C006F0063006B0000000000
It's generally not a question of if, but when. Bummer when there are watches and breakpoints set and N++ has not updated recent changes or files are not saved etc..
Somehow all of the N++ user defined languages got knocked out of the menus. Must make backups sometime.
Edit: Noticed this from the help:
•Notepad++ becomes unstable if property_get fails, which is particularly problematic in light of the above. As a workaround, AutoHotkey sends an empty property instead of an error code when a non-existent or invalid variable is requested.
Since the clean up some of the code in the program, the debugger and N++ have been playing nice.