You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Fred Preston (JIRA)" <ax...@ws.apache.org> on 2006/04/05 14:28:21 UTC
[jira] Updated: (AXISCPP-729) Trace: Unwind the call stack when
exceptions are thrown
[ http://issues.apache.org/jira/browse/AXISCPP-729?page=all ]
Fred Preston updated AXISCPP-729:
---------------------------------
Assign To: (was: Mark Whitlock)
> Trace: Unwind the call stack when exceptions are thrown
> -------------------------------------------------------
>
> Key: AXISCPP-729
> URL: http://issues.apache.org/jira/browse/AXISCPP-729
> Project: Axis-C++
> Type: Bug
> Components: Trace Utility
> Reporter: Mark Whitlock
>
> When Axis C++ throws exceptions, the trace analyzer tool does not realise that the call stack should be unwound. Consequently, it appears in the trace that the method that threw the exception calls the method that catches the exception. For traces that contain many exceptions, the call stack just keeps on getting deeper. This makes the trace very hard to read. The solution to this is to use the "throw out" trace type so that trace statements that throw an exception cause the stack to unwind as shown by the tool.
> This problem was originally described in AXISCPP-406, which also contained a variety of other problems. AXISCPP-406 has now been closed and separate JIRAs raised for the remaining problems.
> Please note that this JIRA is different from (although related to) AXISCPP-424 which adds in throw trace properly (which is a lot more work than this JIRA).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira