Debugger hardly usable after r49328
Original Reporter info from Mantis: wp @wpam
-
Reporter name:
Original Reporter info from Mantis: wp @wpam
- Reporter name:
Description:
After updating svn today I saw that it is no longer possible to inspect variable values in the debugger. Instead, the program hangs and has to be aborted.
Since there is a recent commit related to the debugger in the svn log (r49328) I reverted to the revision immediately before it (r49327). In this revision, the debugger works fine. Going to r49328 brings the issue back.
Steps to reproduce:
- Load attached demo
- Set a breakpoint at line 18 within the for loop
- Run
- The program stops at line 18 as expected
- Press F8 or F9 for a few time to see that the programm is still responsive.
- Now move the mouse above any variable.
- A tooltip should pop up showing the current value of the variable. This does not occur.
- Press F8 or F9 again. Nothing happens.
- Delete the breakpoint. Press F8/F9 again. Nothing happens --> the program hangs.
- Stop the program (Ctrl-F2)
- Add the breakpoint again
- Restart
- When the program stops at the breakpoint, open the "Evaluate/Modify", enter the name of the variable.
- But a debugger messages comes up saying "The debugger experienced an unknown condition" / Exception Access violation / Context: TGDBMIDebuggerCommandEvaluate. State dsPause"
Click "Ignore", the program continues.
Mantis conversion info:
- Mantis ID: 28306
- Version: 1.5 (SVN)
- Fixed in revision: r49396 (#c20f70ce)
- Monitored by: » luizamerico (Luiz Americo), » @martin_frb (Martin Friebe)