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

This is a discussion on how to deal with valueless callstack when an exception finally propagated from unmanaged code to managed code? - DOTNET ; 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 ...

+ Reply to Thread
Results 1 to 2 of 2

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

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

    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.

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

    Hi,

    You should consider using WinDBG -
    http://www.microsoft.com/whdc/devtoo.../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.


    "dotNeter" <Buddhist.CHinA> wrote in message
    news:1179193962.485694.39880@p77g2000hsh.googlegroups.com...
    > 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 Thread
« Change backcolor of the checkbox component | Instantiation via Class Name »

Similar Threads

  1. Converting GDI+ Bitmap from unmanaged code to managed code
    By Application Development in forum DOTNET
    Replies: 3
    Last Post: 09-11-2007, 11:48 AM
  2. calling unmanaged code from managed code
    By Application Development in forum DOTNET
    Replies: 3
    Last Post: 05-29-2007, 10:17 AM
  3. Passing a structure from unmanaged (C++ DLL) code to managed code (C#)
    By Application Development in forum CSharp
    Replies: 0
    Last Post: 05-10-2007, 09:52 AM
  4. Calling managed code from unmanaged code not using COM?
    By Application Development in forum DOTNET
    Replies: 2
    Last Post: 08-16-2006, 02:51 AM
  5. reserving array in unmanaged code and pass it to managed code
    By Application Development in forum DOTNET
    Replies: 0
    Last Post: 06-08-2006, 05:48 AM