No symbols in vcd file

I hope this bug can be fixed as soon as possible. It's really a big trouble for our team, both all of us have updated.

Unfortunately, this "Install Another Version" feature doesn't work. I have autoupdate extensions disabled but it updates to 0. That was driving me nuts. It kept updating and I couldn't figure out why. Okay, we plan to release a 0. See This appears to be fixed by: VamosCC Your scenario is probably different with the same symptom. Can you open a new issue with more repro details? You may want to close all VS Code instances and then make sure all the cpptools process are killed -- otherwise, those processes can lock the database and prevent the Outline from populating.

Skip to content. Star 4. New issue. Jump to bottom. Can you tell if it has crashed? Sorry, something went wrong. Looking at the Activity Monitor, the Microsoft. Yeah, it looks like our process is crashing the main thread is crashing, but the process remains. Can you get any crash info on the Mac?

Windows has an Event Viewer with crashes logged and I remember Mac had something similar. We need to get a call stack or repro. Narrowing down the repro steps would also help. Or if you can repro the bug on Windows we could get a dmp that way. Can you open your folder without opening any files while the Mac config in the bottom right is red and wait till it is white?

It's possible that a file is causing our parser to crash due to unexpected characters. If you could open a smaller workspace or add files. Also, the thing that worked for me was deleting all the output files manually , Clean won't do it every time and that's why even though the.

Delete all files in the bin and obj folders. Then build the solution again. Good Luck! Make a copy of your "Debug" folder within your project's folder, then delete every file in the original "Debug" folder. As additional measure if you had your visual studio already running with your project loaded, close it after deleting Debug's contain and reopen it before re-build the whole project, theoretically this action will create new copy of symbol files and the rest needed to debug your code.

I found out this problem occurred to me when I moved my files to other computer and try to compile and debug my code from there, although all folder and drive names were the same, some how the IDE was unable to use the previously created symbol files. Hope this work around works for some one else!. I ran into the same problem after cancelling the loading of symbols whilst attempting to debug my application in VS Solutions above did not work for me, but this did.

Maybe this will help as a workaround for someone Make sure the driver is installed correctly. Then I realized that it is due to DLL dependency.

Pay attention, copy to System32, or it won't work for me. Scroll down to w3wp. Check "Show processes from all users. After refresh scroll again to w3wp. Initially, I had no issue with debugging my program but after tweaking here and there the issue that OP says began to arise. The module and its symbols were loaded and nothing in this guide seemed to correspond to my problem. I'm not sure why, but, it's sort of a compiler behavior I haven't been experienced before.

In my case, the error was due to the fact that part of the code was connected as an external library. In order for debug process to work also when going into the code of the external library, it was necessary to add not only its headers, but also the implementation files - folder Source Files of Solution Explorer. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow.

Learn more. Asked 10 years, 1 month ago. However, when trying to compile the. No symbols have been loaded for this document. However, I don't get why Visual Studio doesn't find it. Still, Visual Studio is complaining that it doesn't have loaded any symbols. In the output console, it also tells me that it has loaded the symbols of the. Am I missing somewhat? When you compile the. What version of Visual Studio?

Are all the projects in the same solution? Then Visual Studio handles linking everything up, and the. Also, if you use LoadLibrary to load the DLL the debugger won't load the debug info and won't know where to set the breakpoints in the DLL until after it is loaded, which can cause the error you are seeing as well.