Hello,
have implemented a global exception handler. If an exception occurs, the
event OnThreadExcepti on will be called. In this method I call
Debugger.Launch () to start a debugger. This works so far but the call stack
doesn't show the path to the location where the exception occured to obtain
more information about the failure.
When OnThreadExcepti on is called , the call stack is cleared. How can it be
accomplished, that debugging at the location of the failure still is
possible, when an executable created
with debug information is started stand alone, the exception occurs and the
debugger is launched from inside the OnThreadExcepti on method.
Has really nobody an answer to this question?
Diana
have implemented a global exception handler. If an exception occurs, the
event OnThreadExcepti on will be called. In this method I call
Debugger.Launch () to start a debugger. This works so far but the call stack
doesn't show the path to the location where the exception occured to obtain
more information about the failure.
When OnThreadExcepti on is called , the call stack is cleared. How can it be
accomplished, that debugging at the location of the failure still is
possible, when an executable created
with debug information is started stand alone, the exception occurs and the
debugger is launched from inside the OnThreadExcepti on method.
Has really nobody an answer to this question?
Diana