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 ax...@ws.apache.org on 2004/09/21 15:44:39 UTC

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

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
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: New Feature

     Status: Open
   Priority: Major

    Project: Axis-C++
 Components: 
             Basic Architecture

   Assignee: Mark Whitlock
   Reporter: Mark Whitlock

    Created: Tue, 21 Sep 2004 6:43 AM
    Updated: Tue, 21 Sep 2004 6:43 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


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

Posted by "John Hawkins (JIRA)" <ax...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/AXISCPP-164?page=comments#action_58369 ]
     
John Hawkins commented on AXISCPP-164:
--------------------------------------

All but start-up trace are complete. Startup will be done in 1.5 but the rest is not going to be done.

> Not all Axis C++ code entry/exit traced
> ---------------------------------------
>
>          Key: AXISCPP-164
>          URL: http://issues.apache.org/jira/browse/AXISCPP-164
>      Project: Axis-C++
>         Type: Improvement
>   Components: Basic Architecture
>     Versions: future (enh)
>     Reporter: Mark Whitlock
>     Assignee: Mark Whitlock

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

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


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

Posted by "Mark Whitlock (JIRA)" <ax...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/AXISCPP-164?page=history ]
     
Mark Whitlock closed AXISCPP-164:
---------------------------------

     Resolution: Fixed
    Fix Version: 1.5 Beta

I have now implemented startup trace. Throw trace is the subject of a separate JIRA. The other problems in this JIRA are either implemented or there are no plans to implement them.

> Not all Axis C++ code entry/exit traced
> ---------------------------------------
>
>          Key: AXISCPP-164
>          URL: http://issues.apache.org/jira/browse/AXISCPP-164
>      Project: Axis-C++
>         Type: Improvement
>   Components: Trace Utility
>     Versions: future (enh)
>     Reporter: Mark Whitlock
>     Assignee: Mark Whitlock
>      Fix For: 1.5 Beta

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

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


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

Posted by "Mark Whitlock (JIRA)" <ax...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/AXISCPP-164?page=comments#action_58372 ]
     
Mark Whitlock commented on AXISCPP-164:
---------------------------------------

I would like to add in throw trace as well. Instrument throw statements so they appear in the trace. This is slightly harder than catch trace since the type of what is being thrown is harder to discover.


> Not all Axis C++ code entry/exit traced
> ---------------------------------------
>
>          Key: AXISCPP-164
>          URL: http://issues.apache.org/jira/browse/AXISCPP-164
>      Project: Axis-C++
>         Type: Improvement
>   Components: Basic Architecture
>     Versions: future (enh)
>     Reporter: Mark Whitlock
>     Assignee: Mark Whitlock

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

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


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

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


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

Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/AXISCPP-164?page=history ]

Samisa Abeysinghe updated AXISCPP-164:
--------------------------------------

    Component: Trace Utility
                   (was: Basic Architecture)

> Not all Axis C++ code entry/exit traced
> ---------------------------------------
>
>          Key: AXISCPP-164
>          URL: http://issues.apache.org/jira/browse/AXISCPP-164
>      Project: Axis-C++
>         Type: Improvement
>   Components: Trace Utility
>     Versions: future (enh)
>     Reporter: Mark Whitlock
>     Assignee: Mark Whitlock

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

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