Object Identity in Managed Debugging

re: Object Identity in Managed Debugging

Javier Luna — Sun, 09 Jan 2005 07:15:00 GMT

Nice post...!!!

re: Object Identity in Managed Debugging

Nicholas Allen — Sun, 09 Jan 2005 07:38:00 GMT

You were careful to point out that ICorDebugHandleValue does not correspond to a GCHandle. What exactly is one of these handle values, then? And how is this scheme different from keeping a map from pseudo variables to GCHandles created by GCHandle.Alloc?

Also, does a 'weak' handle value work like a Weak GCHandle, or a WeakTrackResurrection?

re: Object Identity in Managed Debugging

Matthias — Sun, 09 Jan 2005 14:04:00 GMT

Cool. I had been wishing for something like that. Actually, I would prefer giving a nice name myself to it, instead of "#1".

re: Object Identity in Managed Debugging

Mike Stall — Tue, 11 Jan 2005 09:49:00 GMT

Nicholas -
From the debugger's perspective, System.Runtime.InteropServices.GCHandle is "just" data. The debugger doesn't try to assign any meaning to that data.

Now both the managed GCHandle class and the ICorDebugHandleValue object have an underlying gc reference. The GCHandle class exposes it for managed code; the ICorDebugHandleValue exposes it for the debugger.

It's true that the debugger could get similar functionality to ICorDebugHandleValue via func-evals + GCHandles. However, func-eval is evil, so we want to provide an alternative, more-correct, solution.

weak="track resurection".

re: Object Identity in Managed Debugging

Mike Stall — Tue, 11 Jan 2005 09:51:00 GMT

Matthias - Note the '1#' is purely an application specific restriction. The debugger could have just as easily supported mapping arbitrary names to values.

For example, MDbg (at least in Beta2) lets you map arbitrary names to values like:
set $my_value=array[5].x

Func-eval is evil

Mike Stall's .NET Debugging Blog — Wed, 23 Mar 2005 07:21:00 GMT

Adding IronPython scripting engine to Mdbg

Mike Stall's .NET Debugging Blog — Thu, 01 Sep 2005 04:49:52 GMT

I hear IronPython is a great managed scripting language to embed in other managed apps, so I thought...

Adding IronPython scripting engine to Mdbg

Mike Stall's .NET Debugging Blog — Thu, 01 Sep 2005 19:43:18 GMT

I hear IronPython is a great managed scripting language to embed in other managed apps, so I thought...

Partition of ICorDebug

Mike Stall's .NET Debugging Blog — Wed, 08 Feb 2006 09:37:14 GMT

The ICorDebug API (the API for debugging managed apps) is about 70 total interfaces.&nbsp; Here is how...

Object Identity in Managed Debugging

meneame.net — Mon, 13 Feb 2006 17:49:57 GMT

The problem:

Perhaps you’ve navigated through a global, local, or parameter while debugging, and then through some ugly series of object references (such as a hash table) to find an object reference. You want to be able to get some identity on that

What does a debugger author need to do to support func-eval?

Mike Stall's .NET Debugging Blog — Sun, 05 Mar 2006 20:47:26 GMT

I've mentioned func-eval (aka property eval) is evil for end-users; but it's also evil if you want to...

Mike Stall's .NET Debugging Blog : What's new in v2.0 CLR Debugging (ICorDebug)?

Mike Stall's .NET Debugging Blog : What's new in v2.0 CLR Debugging (ICorDebug)? — Thu, 13 Jul 2006 19:17:03 GMT

PingBack from http://blogs.msdn.com/jmstall/archive/2005/01/04/346641.aspx

Why are you caching data?

Noticias externas — Tue, 12 Feb 2008 10:19:52 GMT

There are multiple reasons to cache data. For example, are you caching because of a performance issue