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 Mark Whitlock <ma...@uk.ibm.com> on 2004/09/21 16:27:48 UTC

Entry/exit trace - jira AXISCPP-153




Hi,
To fix jira AXISCPP-153, I have added in a tool to instrument the Axis C++
code with entry and exit trace as part of the ant build. By default, this
tool is not run by the build. To run the tool put trace = true in your
platform properties file (or build.xml). Once you have built with trace,
trace can be switched on or off at runtime by including/excluding
ClientLogPath from your axiscpp.conf, as always. This tool is in
ws-axis\c\tools\trace and it is written in java. I (and Andy) have tested
it uninstrumented, instrumented but with trace off and with trace on on
Windows, Linux and AIX.

This is a first version of the trace tool so currently there are lots of
restrictions including...
- only the client is traced
- only method names, not parameters are traced
- AxisTransport and AxisXMLParser libraries are not instrumented or traced
- not all files are instrumented and traced.

Hopefully I will be able to improve entry/exit trace over the next few
weeks. Please use it and let me know what you think,
Mark
Mark Whitlock, IBM

Re: Entry/exit trace - jira AXISCPP-153

Posted by John Hawkins <HA...@uk.ibm.com>.



Hi Mark,

Are you going to update the cvs html pages for this?


John Hawkins




                                                                           
             Mark                                                          
             Whitlock/UK/IBM@I                                             
             BMGB                                                       To 
                                       axis-c-dev@ws.apache.org            
             21/09/2004 15:27                                           cc 
                                                                           
                                                                   Subject 
             Please respond to         Entry/exit trace - jira AXISCPP-153 
              "Apache AXIS C                                               
             Developers List"                                              
                                                                           
                                                                           
                                                                           
                                                                           








Hi,
To fix jira AXISCPP-153, I have added in a tool to instrument the Axis C++
code with entry and exit trace as part of the ant build. By default, this
tool is not run by the build. To run the tool put trace = true in your
platform properties file (or build.xml). Once you have built with trace,
trace can be switched on or off at runtime by including/excluding
ClientLogPath from your axiscpp.conf, as always. This tool is in
ws-axis\c\tools\trace and it is written in java. I (and Andy) have tested
it uninstrumented, instrumented but with trace off and with trace on on
Windows, Linux and AIX.

This is a first version of the trace tool so currently there are lots of
restrictions including...
- only the client is traced
- only method names, not parameters are traced
- AxisTransport and AxisXMLParser libraries are not instrumented or traced
- not all files are instrumented and traced.

Hopefully I will be able to improve entry/exit trace over the next few
weeks. Please use it and let me know what you think,
Mark
Mark Whitlock, IBM