axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Closed: (AXISCPP-153) Entry and exit trace
Date Tue, 21 Sep 2004 15:44:37 GMT

   The following issue has been closed.

   Resolver: Mark Whitlock
       Date: Tue, 21 Sep 2004 8:44 AM

A first version of the trace entry/exit tool has been added to CVS with the necessary changes
to build.xml to build and run it. By default this tool is not run, but can be activated by
trace=true in a properties file.
View the issue:

Here is an overview of the issue:
        Key: AXISCPP-153
    Summary: Entry and exit trace
       Type: New Feature

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Axis-C++
             Basic Architecture
   Fix Fors:
             1.3 Beta
             1.3 Beta

   Assignee: Mark Whitlock
   Reporter: John Hawkins

    Created: Mon, 6 Sep 2004 9:46 AM
    Updated: Tue, 21 Sep 2004 8:44 AM
    Due:     Thu, 30 Sep 2004 12:00 AM

We would like the ability to trace entry and exit of methods.

When debugging an application remotely i.e. just using log files someone gives you. It is
essential that we can trace the code path. In order to do this we would like the ability to
trace every time a method is entered and every time it is exited. Exceptions are not marked
as exiting a method and should be logged differently.

We would like to supply a solution that allows other users of the code not to have entry and
exit trace as we understand some of the issues with different standards being used in open-source
code (especially as this option will give a performance hit). Therefore, we are creating a
build time system that will add entry and exit trace only if a certain build flag is set.

In addition to the build time flag - entry and exit trace will only come on when the trace
flag (see AxisCPP 152) is set on. This enables us to allow a user to turn trace on only when
we need it.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message