dotnet clr: how to deal with valueless callstack when an exception finally propagated from unmanaged code to managed code? -- dotnet clr

how to deal with valueless callstack when an exception finally propagated from unmanaged code to managed code?

dotNeter
5/14/2007 6:52:42 PM

dotnet clr: Suppose that an exception occured at unmamaged code, and unfortunately
didn't get caught where it should be caught, finally it's caught by
the outermost try/catch block located at managed code. At that moment,
we usually only got poor callstack for managed code, however, it's
valueless for debugging real problem, you know.
How can I deal with this situation? Is there any effective mechanism
to preserve more value callstack and to improve the debugging?
Thanks.

Re: how to deal with valueless callstack when an exception finally propagated from unmanaged code to managed code?

Gaurav Khanna [MSFT]
5/20/2007 1:27:20 AM

Hi,

You should consider using WinDBG -
http://www.microsoft.com/whdc/devtools/debugging/whatsnew.mspx

--

Thanks!
Gaurav
WinToolZone - http://www.wintoolzone.com/
Inside and Out - http://www.wintoolzone.com/blog/
The information in this post is provided "AS IS" with no warranties, and
confers no rights.

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the dotnet clr group.