Closed nickatundo closed 1 year ago
Thanks for reporting this. I will have to investigate.
We handle that case where if you are stepping into a LogPoint, it should stop. See https://github.com/microsoft/MIEngine/blob/b20b747a715a6b07aafc3a2429609d5e7449b3f1/src/OpenDebugAD7/AD7DebugSession.cs#L3461-L3474
This is a regression caused by https://github.com/microsoft/MIEngine/pull/1337.
Investigating a fix.
Fixed with 1.13.5 (pre-release, release candidate): https://github.com/microsoft/vscode-cpptools/releases/tag/v1.13.5
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