Thanks, this is helpful!
On Wed, 10 Apr 2002 20:57:58 -0700, Mahesh Prakriya <[EMAIL PROTECTED]>
wrote:
>- Is it possible to do in-process debugging not in the context
> of a profiler? This would seem to require somehow getting
> an ICorDebug interface from the CLR.
>
>No.
Bummer, but at least I'm not missing something. The Debug API
reference only mentions the profiler as the "most notable example",
which implies that someone thought there should be others...
>- In the Profiler ExceptionThrown callback, one receives an
> ObjectID for the thrown object. One can get the size and
> type from the ICorProfilerInfo calls, but it would seem that
> in order to inspect its value, one would need to somehow coerce
> it into an ICorDebugValue. Any hints? (Yes, I could simply
> dereference the ObjectId, since it's just a pointer into the
> heap, but what if it's a more complicated object?)
>
>Call "GetCurrentException([out] ICorDebugValue **ppExceptionObject);)
This works! But the Debug API reference says it's not implemented
in-process, so presumably that documentation is wrong. This is
even more valuable because I'm just getting a null ObjectID from
the Profiler ExceptionThrown callback. (Though I am getting the
correct ObjectID from ExceptionCatcherEnter.)
-- Richard
You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
