[ http://issues.apache.org/jira/browse/AXISCPP-164?page=comments#action_58372 ] Mark Whitlock commented on AXISCPP-164: ---------------------------------------
I would like to add in throw trace as well. Instrument throw statements so they appear in the trace. This is slightly harder than catch trace since the type of what is being thrown is harder to discover. > Not all Axis C++ code entry/exit traced > --------------------------------------- > > Key: AXISCPP-164 > URL: http://issues.apache.org/jira/browse/AXISCPP-164 > Project: Axis-C++ > Type: Improvement > Components: Basic Architecture > Versions: future (enh) > Reporter: Mark Whitlock > Assignee: Mark Whitlock > > The trace tool enables entry/exit tracing in much of Axis C++. These are bits > that are not traced, but should be... > - AxisTransport and AxisXMLParser dll/so > - Startup before axiscpp.conf is read in. > - A list of files in Exclusion.java which make the trace tool fail > - trace itself (probably reasonable to not be able to trace trace) > The trace tool could also add trace into catch blocks. > Also there are places where the trace tool should do a better job in adding > in trace exit. For instance: void f(int a){if(a){g(a);}else{h(a); return;}} > needs a traceexit before the closing brace (as well as at the return), but > void f(int a){if(a){g(a); return; }else{h(a); return;}} does not. Indeed to > add trace in here would be unreachable code which would be a warning or error > on some platforms. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
