"Visual Studio 2003 Mixed Mode Debugging Crash"

It’s great that 2005 has shipped. I personally enjoy using it for my own pet projects and I’m very pleased. But shipping a V2 also means exposing versioning problems in the V1 design. Such an issue came up on the forums, which basically boils down to: VS 2003 crashes when:1. I install VS20052. I’m interop…

8

VS 2003 can not debug .NET 2.0 apps.

Somebody asked here on the forums if you can use VS 2003 to debug .NET 2.0 (whidbey) apps. Unfortunately, the answer is no.VS 2003 can not debug .NET 2.0 apps.  It is a restriction in the underlying .NET debugging services (see below)You can still use the .NET 2.0 SDK tools (such as Mdbg, DbgClr) to…

6

Why you sometimes get a bogus ContextSwitchDeadLock MDA under the debugger

The ContextSwitchDeadLock MDA (I blogged about MDAs here) sometimes fires under the debugger. MSDN says: It is possible for this MDA to be falsely activated when all of the following conditions are met:    * An application creates COM components from STA threads either directly or indirectly through libraries.    * The application was stopped in the…

1

Symbol API (CorSym.idl) for managed PDBs

From the mailbag:     Just wanted to know if there are plans to ever give us world citizens an API to modify & emit pdb files, at least for managed assemblies.  Good news. You’ve already got them. 1) The CorSym.idl API (exists in sdk, next to where you find CorDebug.idl) is a com-classic API that can read and…

1

MDbg Sample temporarily broken in post-beta 2 builds.

Customers have alerted us that the MDBg sample is broken on post-beta 2 builds. Rick Byers has diagnosed the problem as an issue in the mdbg build and we’re working to update it. I guess there was a VS change that exposed this problem. Rick may blog a more detailed explanation, but I just wanted to…

6

F5 vs. Ctrl-F5

In VS, F5 will launch your application under the debugger. Under the debugger, you’ll hit breakpoints, be able to edit-and-continue, and do all the debugger things you know and love. Ctrl+F5 will launch your application outside of the debugger. This is like launching your app from the "start | run" menu, except VS becomes the…

5

Process X can’t tell if Process Y is being managed debugged.

From the mail bag: Is there a way to determine if a managed debugger is already attached to a given process id? It looks like ICorDebug.CanLaunchOrAttach might be the right API for this (wouldn’t it return FALSE if another debugger is already attached?). However, it seems like this API always returns TRUE. I searched your…

2

Going from IL to Source

Question from the mail bag: I am trying to get some information on what I can do usefully with the “+ 0xnn” part at the end of a call stack line in VS IDE 2003.So when I see (in the call stack window)cf-gfmaa!Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriter1.Write3_ArrayOfExtendedAnnotationElement(System.Object o = {MyStuff.MyClass}) + 0x4f bytes What can I do with the…

1

A common problem: forgetting to call ICorDebugAppDomain::Attach

I notice one of the most common issues folks hit when they try to write their own managed debugger is forgetting to call ICorDebugAppomain::Attach() at the right time. I’ve seen this 3 different times recently. This part of ICorDebug is not documented very well, and so it’s easy to understand the mistakes here.      You need…

2