You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[This is my first bug report here, apologies if I've misunderstood or provided the wrong info]
If a logpoint is hit during a stepping operation (Step Into or Step Over), the program is restarted after the logpoint and simply continues until a breakpoint hits or the program exits. As I understand it, the intention wrt logpoints in C/C++ is to treat them as breakpoints, in which case the program should not be restarted at all.
Environment
Bug Summary and Steps to Reproduce
[This is my first bug report here, apologies if I've misunderstood or provided the wrong info]
If a logpoint is hit during a stepping operation (Step Into or Step Over), the program is restarted after the logpoint and simply continues until a breakpoint hits or the program exits. As I understand it, the intention wrt logpoints in C/C++ is to treat them as breakpoints, in which case the program should not be restarted at all.
To reproduce, with this program:
main()
, ieint x = value()
.value()
, iereturn 7;
.Step Over
or press F10.main()
, ieprintf...
.return 7
line.In the debug console log it can be seen that a
-exec-continue
MI command is issued to restart the program.Debugger Configurations
Debugger Logs
Other Extensions
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: