[AXISCPP-164] Not all Axis C++ code entry/exit traced

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: future (enh)
• Fix Version/s: 1.5 Beta
• Component/s: Trace Utility
• Assignee: Mark Whitlock
• Reporter: Mark Whitlock
• Created: 21/Sep/04 13:43
• Updated: 18/Feb/05 23:51
• Resolved: 18/Feb/05 23:51

Description

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.