Welcome to MSDN Blogs Sign in | Join | Help

October 2005 - Posts

VS2005 ships!

As you've probably already heard by now, VS2005 has shipped ! I've been using VS2005 for a while now (afterall, MDbg only runs on CLR 2. 0). Since I've been so involved in V2.0, I had forgotten how many people are still on V1.1 and V1.0. (update: fixed
Posted by jmstall | 4 Comments
Filed under:

Do printer manufacturers do any scenario testing?

We do a thing called "Scenario Testing" where we run through common end-user scenarios to make sure they work from end to end. This is like the antithesis of unit testing. The reason is that often each single component does the right thing, but when you
Posted by jmstall | 13 Comments
Filed under:

Document properties that don't round-trip.

I personally think most API documentation is lame and either leaves critical behavior qualities unspecified, or don't comment when standard assumptions may be broken. One example is not documenting object lifespans . Another example is that you'd normally
Posted by jmstall | 12 Comments
Filed under:

Update to Iron Python MDbg sample.

Shawn Farkas just let me know that the latest Iron Python 9.3 release breaks my Iron-Python Mdbg sample : So the 0.9.3 release breaks the mdbg extension – the fix is pretty quick though. When creating the streams to redirect stdin, out, and err through
Posted by jmstall | 1 Comments

Informal poll on debugger feature requests?

What new feature requests do you want in the managed debugging services? In other words, if you could spend $100 on the following debugger-related items, how would it break down: 1) Support for debugging a managed dump file (without needing SOS) 2) Data
Posted by jmstall | 23 Comments
Filed under:

New web look

You may have noticed the web page layout of my blog is now different. My reasoning was that it actually renders better this way. I include a lot of tables. In the old layout, there were two sidebars: one on the left and one on the right. If the width
Posted by jmstall | 0 Comments

Big picture on Symbol APIs

Here's how the managed symbol API fits into the overall symbol-store / PDB picture, courtesy of Steve Steiner and Curtis Man. There's a basic uniform low level storage for both managed and native symbols. The low-level API is private, and then there are
Posted by jmstall | 2 Comments
Filed under:

.Net / ASP.Net Developers: check out Tim's blog

Tim Stall writes a .Net blog for .Net Developer’s Journal ( http://timstall.dotnetdevelopersjournal.com ), which I'd like to recommend (you'll notice I've linked him over on the 'links' section). Whereas my blog is very low level and focuses mostly on
Posted by jmstall | 3 Comments
Filed under:

Native threads still run at a managed breakpoint.

When you hit a managed-breakpoint while managed-only debugging, only the managed threads are stopped. So threads that are not running managed code can continue to run and won't stop unless they hit managed code. If a thread was in managed code but called
Posted by jmstall | 1 Comments

Debugging support for ASP.Net

From the CLR perspective, ASP.Net is just another managed application. You can just attach MDbg to it and start debugging. While this works, it has some limitations: You need to: 1) make sure ASP.Net is deployed and started (since MDbg can only attach
Posted by jmstall | 0 Comments

Viewing Exception Message string

Several people have asked how managed debugger tools can print more details about an exception, such as its message string. Just printing that an exception of type "BadArgumentException" was thrown is a nice start. Managed Exceptions are associated with
Posted by jmstall | 1 Comments
Filed under:

Remote Debugging vs. Remote UI

Visual Studio supports "Remote Debugging" ( Gregg talks about that a lot here ), which is the ability for the debugger and debuggee to be on different machines. It turns out the CLR Debugging services don't provide any explicit support for remote debugging.
Posted by jmstall | 1 Comments
Filed under:
 
Page view tracker