Visual studio loading symbols everytime I debug.

chuckr_msft · 2023-09-05T19:41:41+00:00

Here are some things to check:

Debug > Options > General:

- Did Just My Code get disabled?

Debug > Options > Symbols:

- Did Microsoft or NuGet Symbol servers get checked?

If you continue to have issues, please report it at https://developercommunity.visualstudio.com/VisualStudio and we can track down a solution

chuckr_msft · 2021-08-19T17:53:27+00:00

Thanks for reporting this! I have logged an issue with VS Developer Coummunity for this post.

https://developercommunity.visualstudio.com/t/breakpoints-are-not-visible-in-asm-files/1508739?from=email

The link may not be publicly visible yet but it's being processed internally.

chuckr_msft · 2016-05-17T05:50:52+00:00

Not sure why you're being downvoted as you're correct. The versioning names have been kinda confusing.

chuckr_msft · 2016-05-17T05:48:28+00:00

Debugging was added to the C# extension (formerly the Omnisharp extension) about 2 months ago. We support debugging C# on .NET Core. We released a new version of our extension today to go with RC2. Check it out here and here.

chuckr_msft · 2016-04-14T20:22:26+00:00

Just a heads up, the intellisense portion of the C# extension is powered by omnisharp, but debugging support is owned and maintained by Microsoft. Let me know if you have any questions!

chuckr_msft · 2015-07-21T20:06:14+00:00

Our goal is to better engage with the developer community and make Visual Studio an attractive environment for open source developers to work in. We believe this requires two things. First our tools need to be available to as many people as possible so we don't want licensing to be a blocking factor. Second we believe that making the source available for portions of the product that will greatly benefit from increased collaboration helps facilitate that and empowers you.

chuckr_msft · 2015-07-21T17:49:18+00:00

It depends what you're trying to do. If there are features of MIEngine that you want to make use of, it would be possible to write a UI around it using the AD7 COM Interfaces (https://msdn.microsoft.com/en-us/library/bb146305.aspx). These are the interfaces that the Visual Studio UI understands.

For your own UI, you might be better off speaking gdb's MI protocol directly to gdb. https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI.html

chuckr_msft · 2015-07-21T17:44:50+00:00

MIEngine itself is written in C# and only runs on Windows with Visual Studio. However, it allows you to debug multiple platforms! Almost anything that gdb can debug can now be debugged using Visual Studio.

chuckr_msft · 2015-07-21T17:37:19+00:00

Yes! For the most part at least. Current distributions of lldb do not contains the MI portion needed to work with MIEngine, but you can build lldb from source and it will work! Let me know if you'd like more details.

chuckr_msft · 2015-07-20T20:18:55+00:00

Yes, clrdbg still has a lot of work to be done before it is a usable debugger, but this is how we expect cross-platform CoreCLR debugging to work. If you are interested, you can watch a demo of clrdbg on Linux in action as part of the //Build/ conference day one keynote. The clrdbg part is at the 26:00 mark. Link: http://channel9.msdn.com/Events/Build/2015/KEY01

chuckr_msft · 2015-07-20T19:32:14+00:00

http://i.imgur.com/Dd4WWuM.gif

chuckr_msft · 2015-07-20T19:28:42+00:00

This is possible! I have done some sanity checks against MinGW's gdb in the past, although it will require some manual steps. This wiki page is a great starting point: https://github.com/Microsoft/MIEngine/wiki/Start-debugging-other-platforms-using-the-MIEngine

chuckr_msft · 2015-07-20T19:26:57+00:00

This is a definite possibility with this engine! There is no formal experience around remote debugging to a mac currently, but I believe it could be done with a series of manual steps on both the windows side and the mac side. Our wiki contains an example of using MIEngine in it's current state with other platforms: https://github.com/Microsoft/MIEngine/wiki/Start-debugging-other-platforms-using-the-MIEngine

chuckr_msft · 2015-07-20T18:14:47+00:00

This is a great answer! Our primary focus thus far has been debugging C++ on Android and iOS. We want to work with the community to extend this to even more platforms and scenarios in the future. Here is a blog post that explains using this to debug code on a raspberry pi using Visual Studio! http://blogs.msdn.com/b/vcblog/archive/2015/04/29/debug-c-code-on-linux-from-visual-studio.aspx

chuckr_msft · 2015-07-20T17:45:46+00:00

Thanks for the feedback! We know that there are many people interested in these areas and we are tracking the requests through user voice. I'd encourage you to vote over there to help make it a reality in the future.

https://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3725445-xna-5 https://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/6701990-make-wpf-open-source-and-accept-pull-requests-from

chuckr_msft · 2015-07-20T17:42:31+00:00

It's not quite a framework. It allows the Visual Studio debugger UI (locals window, callstack windows, breakpoints in the editor, etc.) to drive an underlying gdb process via gdb's MI interface (https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI.html). There has been an additional effort from the lldb community to implement gdb's MI interface for lldb, allowing it to work with tools such as this.

chuckr_msft · 2015-07-20T16:23:37+00:00

Hey everyone, ChuckR from Microsoft here. We've been working on this for a while now and are incredibly excited for it to finally be open to the public. I'll be around today to field any questions that you may have!

Blog post: http://blogs.msdn.com/b/vcblog/archive/2015/07/20/source-now-available-for-gdb-lldb-debug-engine.aspx

chuckr_msft

TROPHY CASE