Are there any plans to support the `cppvsdbg` type in the future?

Discussion
1

I experienced that when I want to debug MSVC cpp code on cursor, it says that cppvsdbg is not supported.
I found it mentioned a long time ago on github, but didn’t find a corresponding solution to debugging MSVC cpp code.

So I’m asking if there’s a plan to follow up and address this issue?
Or is there another way to fix it?

image

3 Likes
2

Yes I would like to know this too. Configured debug type 'cppvsdbg' is installed by not supported in this environment · Issue #861 · getcursor/cursor · GitHub has been around for a year now. I just discovered Cursor but not being able to use it for C++ is pretty rough. I like it enough that I really want to press this with customer support. Can we ever expect this to work?

3

Someone posted an answer on the github page, but it’s not good. Microsoft only licenses the cppvsdbg debugger for VScode and open-source derivatives of VScode. It sounds like cursor.ai can’t be made to work with cppvsdbg because of its proprietary nature; that it would be against the cppvsdbg license.

So there might not be any solution to this.

1 Like
4

There is a thread at How can I use the `vsdbg` adapter? · mfussenegger/nvim-dap · Discussion #869 · GitHub where this issue is discussed, along with a workaround. Maybe we could join forces and implement a “solution”? Anyone comfortable with the debug adapter protocol? The idea is to re-route the handshake to be signed using a running vscode instance.

5

I have been trying to get clang-d (lldb) instead of cppvsdbg to no success (I could via vscode, but I suspect it falls back or uses features of cppvsdbg?). it’d be nice if there was an official guide how to debug cpp apps compiled with msvc on windows.

6

OMG, guys, I’ve just discovered this, it’s a disaster! Whether you like it or not, people do develop with MSVC, you must support its debugging! What’s the point of all these AI features, if users cannot program in the IDE?!

1 Like
7

It is an issue of licensing; as long as it is closed source. In cases like CLion, they have a wrapper around lldb that works out of the box for debugging a MSVC project. Cursor probably expects us to use other debugger on our own. Setting it up a regular lldb is painful (python version mismatch cause debugger to fail) and doesn’t show std types unless you format it and it is also terribly slow.