visual-studio-debugging

问题 When debugging my project in visual studio (2010) I get the message " no source available " once I step into one of my files. The file is now just a test file with one function: void foo() { float testbuf[200000] = {0}; } If i allocate a smaller buffer the debugger enters the file normally. In my debugging view my "call stack location" is empty and there is "no disassembly available". It looks to me like there is a maximum amount of data that the visual studio debugger can handle or something

问题 I am getting this error running Nodejs from Visual Studio 2017 since i upgrade NodeJs. Also breakpoints are not working. Any way to fix this? Note: VS version is 15.5.6 NodeJS version 8.9.4 回答1: I was having the same issue, and following has worked for me. 1st solution change in your launch.json from < "protocol": "legacy", > "protocol": "auto", This should work. 2nd solution In package.json: scripts: { "debug": "DEBUG=pd* nodemon --inspect-brk --harmony --nolazy server.js" } Then default

问题 Visual Studio 2013 Professional crashes when I try to open the Debug tab in the properties panel of a Windows Phone 8 project. No error given only "Microsoft Visual Studio 2013 has stopped working". Attached Visual Studio as a debugger and got the following error: An unhandled exception of type 'System.NullReferenceException' occurred in Microsoft.VisualStudio.SmartDevice.ProjectSystem.Base.dll I'm running Visual Studio as an Administrator 回答1: I have the same problem with a very weird

问题 I'm injecting a dll into a third party program and debugging that dll with MSVC. I have been doing normally for some time until a recent update to the program now causes MSVC to crash each time I attach the debugger to the process while my dll is injected. My dll still runs normally, I just cannot debug it as attaching MSVC crashes the host program. Event view shows this: Faulting application name: SomeApp.exe, version: 1.0.1023.0, time stamp: 0x5109728a Faulting module name: MyDLL.dll,

问题 For example, doing something like this: foreach (DataRow row in data.Rows) { Person newPerson = new Person() { Id = row.Field<int>("Id"), Name = row.Field<string>("Name"), LastName = row.Field<string>("LastName"), DateOfBirth = row.Field<DateTime>("DateOfBirth") }; people.Add(newPerson); } Setting a breakpoint to an individual assignation is not possible, the breakpoint is set to the entire block. If I want to see specifically where my code is breaking, I have to use: foreach (DataRow row in

问题 I am going to use #if DEBUG directive in a class library. The compiled ClassLibrary.dll will be used in a separate Application.exe. Will my debug code from this class library be executed in the following situations? library is compiled in DEBUG mode, application is compiled in RELEASE library is compiled in RELEASE, application is compiled in DEBUG 回答1: A compiler directive is interpreted at compile time and not at runtime. Therefore it does not matter, if the using application is compiled in

问题 I've got this code: String testData = File.ReadAllText("siteQueryTest.txt"); XDocument xmlDoc = XDocument.Parse(testData); List<SiteQuery> sitequeries = (from sitequery in xmlDoc.Descendants("SiteQuery") select new SiteQuery { Id = Convert.ToInt32(sitequery.Element("Id").Value), UPCPackSize = Convert.ToInt32(sitequery.Element("UPCPackSize").Value), UPC_Code = sitequery.Element("UPC_Code").Value, crvId = sitequery.Element("crvId").Value, dept = Convert.ToInt32(sitequery.Element("dept").Value),

问题 I've got a crash in our app which I can't debug as one of our partners has seen fit to use truly horrible 'CodeMeter' to encrypt their DLL. CodeMeter licensing prevents all attempts to debug an app containing a CodeMeter encrypted DLL and even seems to cause MiniDumpWriteDump called from an unhandled exception filter to fail (this technique works without this DLL loaded). The crash only happens when the encrypted DLL is loaded into the process. I'm going mad trying to debug this and establish

问题 Things I've done: On both the default website and my virtual folder in IIS Manager -Enabled Parent Paths -Set Enable Server Side Debugging to be True Set Breakpoints in my code by 1) F9 2) Using the Stop command 3) Purposefully put mispelled commands in my VBScript to force the debugger to attach I've then tried starting the website without debugging and attaching to W3wp.exe/ DLLHost.exe Have also tried running the website in visual studio in debug mode Is there something I'm missing or

问题 How do I create short-cuts in visual studio 2012 for "Disable all breakpoints" and "Enable all breakpoints"? Thanks in advance! 回答1: Tools -> Options -> Environment : Keyboard Scroll down to Debug.DisableAllBreakpoints Mark it as a global hotkey. And press a combo. Rinse, Repeat for Debug.EnableAllBreakpoints 来源： https://stackoverflow.com/questions/19456179/vs-2012-add-shortcuts-for-disable-all-breakpoints-and-enable-all-breakpoints