Stop debugging C# code in Visual Studio.Start debugging C# code in Visual Studio.Fix C# code by debugging in Visual Studio.Though that's not a very good solution and odd that it works. The most reliable method I've found is to let it load all symbols from the Microsoft Symbol Servers for one to three runs, and then once that stops working clear the cache and run it completely locally one time, then go back to the Microsoft Symbol Servers. It will very randomly work perfectly but then restarting the program, while changing literally nothing, will make the problems come back. Note that deleting all breakpoints, a common solution to these types of problems, has no effect. I've essentially tried all the possible configurations in Options->Debug->Symbols, including enabling and disabling the Microsoft Symbol Servers, explicitly giving it the location where these libraries should be located, project directories, loading all modules or only specified modules, clearing the cache, excluding the libraries that cause freezes (they still load+freeze,) etc I've let it sit over night and once if freezes it never seems to recover. Per the debugger it'll freeze while trying to load symbols from libraries such as:Īnd a number of others. I'm attempting to debug a C++ application written by someone else, same code runs without issues on several other computers but freezes on my computer when opening a windows file dialog (for opening or saving files.)
The project developers seem to have no idea and I don't think it's related to their code but rather my setup. I've been stuck on this issue for several days now and scoured all remotely related stackoverflow answers I can find with no solutions working. *On Windows 7, Visual Studio 2012 Professional, if it's relevant.
0 kommentar(er)
