[Mono-dev] [MonoDevelop] Some questions about the debugger/debugger add-in

[Casey Marshall]

On Wed, 2008-07-16 at 20:33 +0200, Lluis Sanchez Gual wrote:
> El dc 16 de 07 de 2008 a les 11:19 -0700, en/na Casey Marshall va
> escriure:
> > On Wed, 2008-07-16 at 10:30 -0700, Casey Marshall wrote:
> > > On Wed, 2008-07-16 at 15:00 +0200, Lluis Sanchez Gual wrote:
> > > > El dt 15 de 07 de 2008 a les 17:34 -0700, en/na Casey Marshall va
> > > > escriure:
> > > > > Some of the views that exist now are pretty neat, but what about things
> > > > > like, say, visually inspecting variables while debugging, 
> > > > 
> > > > You can already do that.
> > > > 
> > > 
> > > Yeah, I did notice that after sending that mail. I was expecting
> > > something more direct than a tooltip.
> 
> What can be more direct than a tooltip? In any case, you can also use
> the watch window.
> 

By direct I meant "doing something," like right-clicking on it, not
hovering over the field momentarily -- i.e., deliberately doing nothing.
That's just an opinion.

> > > 
> > 
> > Oh, but expanding an object is pretty unusably slow at this point -- it
> > takes a full minute to resolve each property of an object. I assume that
> > this is in the debugger itself?
> 
> Expanding an object should not be slow. Which is the type of the object?
> does it have many properties?
> 

One class in particular only has four properties, but I added a little
monitor around the 'Wait' in DebuggerServer.RuntimeInvoke, and the wait
is taking a full minute per property. I haven't looked deeper.

I'm not discounting that this is a local problem, though. I'm running on
x86.

Also, in ExpressionEvaluator.cs:94, creating the IntPtr sometimes throws
an OverflowException, since IntPtr rejects long values that don't fit in
a Int32, though the value it has in this case does fit in a UInt32. I'm
not sure which is wrong, though: the check in IntPtr, or the MD code.