-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve vs2015 debugger user-experience #149
Comments
Not sure about #3: the ability to specify command line args and working directory is still useful. Besides, in VS2013 we support launching under the built-in debugger. |
I meant plugin-wide options in Tools/Options settings (edited first post to clarify). |
That's true, although I personally would prefer some debugger vs no debugger at all. There's also cv2pdb... |
Well, yeah, there's cv2pdb, but I think it's better to just wait for Microsoft to open-source their gdb support and use it in 0.2 (or 0.3) for both vs2013 and vs2015 and in 0.1.1 just have no debugging (unless you have vs2015 + C++ Mobile plugin). |
The GDB engine for Visual Studio is now open source. |
I've just tried ripping off MIEngine and shipping it with Visual Rust works OK (modulo some changes). I'll upload the repos tomorrow. |
Closed by #177 |
As of #145, we've now got 2015 debug support. There are still some ways to make it nicer for general consumption.
Don't launch debugger at all if no gdb foundGray-out plugin-wide debugging settings (Tools/Options/...) with a short message how you can get it working (vs2015 + C++ mobile tools)%PATH%
when launching the debuggerIn the future we might want to bundle gdb.exe.
The text was updated successfully, but these errors were encountered: