On 25/06/2006, at 12:36 AM, Dan Stenning wrote:
http://www.realsoftware.com/feedback/viewreport.php?reportid=gebfxuir
I have a try/catch called at a high level to catch all unhandled
exceptions.
however when an error such as NILOBJECT is encountered, the
breakpoint
stops on the catch ( correctly) but the call stack does not show the
erroneous method and its call history.
The stack has been cleared at this point and destructors run for
local objects. An exception handler is not "called".
Instead, only the call to the very
high level method ( in which the try/catch code was placed ) is
shown. This
is useless debugging wise.
as I have just appended to the report:
The requirement of preserving the entire call stack every time there
is an exception thrown is complex and would be expensive both to
implement and at runtime.
I think it would be far better to allow for breaking at exceptions
regardless of whether they are handled and to allow more detailed
specification of which exceptions are intercepted by the debugger, as
done in Visual Studio.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
