January 2004 - Posts
A few of my coworkers also started blogs this week: http://blogs.msdn.com/andypennell http://blogs.msdn.com/stevejs If anyone else has a debugger related blog, please add it to the comments.
Read More...
The Visual Studio debugger supports debugging both .NET code and native code at the same time. We call this ‘interop’. At first glance, this might not seem like much of an accomplishment. After all, we support debugging .NET code well enough,
Read More...
I have been doing some page fault analysis lately, and I decided to share what I have learned. First, there are two basic types of page faults -- soft faults and hard faults. A hard fault is a true page fault where the operating system needs to read data
Read More...
If stepping in the debugger is taking too long, here are a few suggestions on improving your experience: Close any Windows that you don't need. The modules Window and disassembly Window are good candidates if you have them open. If you are 'mixed' debugging
Read More...
A coworker maintains a FAQ for some of the most frequent 7.0/7.1 debugger problems. http://www.gotdotnet.com/team/csharp/learn/whitepapers/howtosolvedebuggerproblems.doc
Read More...
A while back, I found a problem where I was getting a stack overflow exception inside of chkstk. Chkstk is a crt function and can probably be found in every dll. In my case the crash didn't make sense because I clearly had plenty of stack space left.
Read More...
Recently, I have been looking at memory usage. Up until this point, I have been using working set to tell me how much physical memory a process is using. It turns out that this definition is wrong. Working set actually tells you how many virtual pages
Read More...
My name is Gregg Miskelly. I am a developer on the Visual Studio team working on the debugger. I decided to start a blog because I couldn’t find any other blog that talked about Debuggers. I will probably also talk a bit about performance, since
Read More...
