axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From axis-c-...@ws.apache.org
Subject [jira] Created: (AXISCPP-153) Entry and exit trace
Date Mon, 06 Sep 2004 16:48:36 GMT
Message:

  A new issue has been created in JIRA.

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

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

     Status: Unassigned
   Priority: Major

    Project: Axis-C++
 Components: 
             Basic Architecture
   Versions:
             1.3 Beta

   Assignee: 
   Reporter: John Hawkins

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

Description:
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.


---------------------------------------------------------------------
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


Mime
View raw message