[jira] Updated: (AXISCPP-164) Not all Axis C++ code entry/exit traced

[ax...@ws.apache.org]

The following issue has been updated:

    Updater: John Hawkins (mailto:hawkinsj@uk.ibm.com)
       Date: Fri, 15 Oct 2004 3:34 AM
    Changes:
             type changed from New Feature to Improvement
             Version changed to future (enh)
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/AXISCPP-164?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXISCPP-164

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXISCPP-164
    Summary: Not all Axis C++ code entry/exit traced
       Type: Improvement

     Status: Open
   Priority: Major

    Project: Axis-C++
 Components: 
             Basic Architecture
   Versions:
             future (enh)

   Assignee: Mark Whitlock
   Reporter: Mark Whitlock

    Created: Tue, 21 Sep 2004 6:43 AM
    Updated: Fri, 15 Oct 2004 3:34 AM

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.


---------------------------------------------------------------------
JIRA INFORMATION:
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