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

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

dotNeter - 15 May 2007 02:52 GMT

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.

Reply to this Message

Gaurav Khanna [MSFT] - 20 May 2007 09:27 GMT

Hi,

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

Signature

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.

> Suppose that an exception occured at unmamaged code, and unfortunately
> didn't get caught where it should be caught, finally it's caught by
[quoted text clipped - 4 lines]
> to preserve more value callstack and to improve the debugging?
> Thanks.

Reply to this Message

Rate this thread:

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

Free Magazines