Re: Close but no cigar


> PS So it's very much a command line experience for the moment ?
> You can't call up the call stack window, double click on it and the source
> code pops up - if it's on the machine ? Or hover over variables and their
> value shows up as hovering help ? This seems puzzling because if VS.NET can
> debug a C# app that's running under it, what's the difference ? Why the
> degradation of the debugging experience ?
>
> Just wondered ....
>

AFAIK the main difference is that CLR debugging support is implemented
in-process (there are helper threads in the debuggee process that manage
the debuggee state and can provide this state information to an external
debugger via COM interfaces).

When debugging a dump, there is no in-process helper, so the debugger
has to rely on something like SOS to interpret internal CLR data structures.

Here you can find some related information:
http://blogs.msdn.com/jmstall/archive/2004/10/13/241828.aspx

Oleg






.

Loading