Vscode-cpptools: [Feature Request] Logpoint support for cppdbg, cppvsdbg

[aguirreeng]

Type: Debugger

Just a quick question. Are logpoints supposed to be working for C++ debugging?

I can add the logpoint and the debugger actually stops at the point, but no message is logged (or at least I can't find it).

• OS and Version: Windows 10
• VS Code Version: 1.27.2
• C/C++ Extension Version: 0.19.0

[pieandcakes]

I am assuming you are talking about this?

We haven't done any work to support this yet. Are you using gdb/lldb or the Visual C++ debugger?

[pieandcakes]

Relevant Protocol Changes: https://github.com/Microsoft/vscode-debugadapter-node/commit/aeda2ba8ae526906585a5ccb7d8346a71b83ed10

[aguirreeng]

That is exactly what I was talking about!
I'm using Visual C++ debugger.

[britalmeida]

Using gdb here, and it also looks like logpoints are doing the exact same as regular breakpoints.

[dreignier]

Same issue for me.

• gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
• GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git

Visual studio code "about":
Version: 1.33.1
Commit: 51b0b28134d51361cf996d2f0a1c698247aeabd8
Date: 2019-04-11T08:20:22.771Z
Electron: 3.1.6
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Linux x64 4.15.0-46-generic

[dwlsalmeida]

Also affected. Very confused until I found this.

[JoeyRxy]

please support logpoint.thx

[djadeja]

Please, support logpoint.
Thanks

[djadeja]

Please provide primary information, for doing analysis on how can it be added in C/C++ Debug Adapter. So, that it can be added by community developers or users.

[pieandcakes]

@djadeja Our repository contains details on how to debug MIEngine which is what drives the debug adapter.

[guestieng]

Can the current state of this issue be made clearer?
I am referring to unexpected behaviour described in https://github.com/microsoft/vscode-cpptools/issues/5247#issue-593299303,
i.e. still facing the problem of erroneous, respectively missing, logging functionality with Visual C++ debugger (MSVC, cppvsdbg !).
So is there any solution/workaround for this problem already?
(as I understand, the debug MIEngine does only help for gdb/lldb, isn't it?)

[anmace]

I am seeing this issue in VS Code version 1.44.2. I am trying to debug an accessibility bug using Narrator but instead of logging text, the log breakpoints are breaking like regular breakpoints and are taking focus away from the Window and Narrator starts reading the VS Code window instead. I need to keep Narrator's focus on the Window I am debugging the entire time, otherwise it is impossible for me to properly debug Narrator's behaviour.

This really seems like a bug with log breakpoints rather than a feature request. Are log breakpoints working at all for others in C++ VS Code at the moment? Can this please be fixed soon? It is really impacting my ability to debug accessibility bugs because it steals focus.

[jasjivsk]

Could dprintfs use as setting logpoints?

https://doc.ecoscentric.com/gnutools/doc/gdb/Dynamic-Printf.html

[jasjivsk]

As dprintfs will not break the execution of the code and print the statements on the debug console.

[anmace]

Thanks, I will try using dprintfs

[jasjivsk]

@pieandcakes, Could dprintfs be implemented in vscode as logpoints?

[bshoshany]

Adding to this issue because I'm having the same problem... Logpoints work perfectly with GCC (print a log message to the Debug Console and do not break execution), but with MSVC they just act as regular breakpoints (do not print a log message to the Debug Console and do break execution).

Version: 1.51.1 (user setup)
Commit: e5a624b788d92b8d34d1392e4c4d9789406efe8f
Date: 2020-11-10T23:34:32.027Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.19042
C/C++ extension version: 1.1.3

[simonrenger]

Same as @bshoshany