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. 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. This makes it hard to figure out the location of the cause, since the entire call path leading up to the exception is lost. If anyone else has this issue and would like RB to change how things work in the debugger to alleviate this, please add yourself to the watch list re the link or discuss here. -- 13flatFIVE C++ Source Conversion services for RB developers http://www.13flatfive.com/squirt.html _______________________________________________ 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>
