[jira] Commented: (AXISCPP-165) Improve trace readability

["Mark Whitlock (JIRA)" <ax...@ws.apache.org>]

     [ http://issues.apache.org/jira/browse/AXISCPP-165?page=comments#action_54609 ]
     
Mark Whitlock commented on AXISCPP-165:
---------------------------------------

Tracing "this" for instance methods is slightly harder than I first thought because "this" will not compile if used in static methods or C functions. So the trace tool has to be able to recognise the difference between static and instance methods. But there is nothing on the method declaration in the .cpp file that tells the trace tool - the static keyword is in the header file where the class is defined. So the trace tool will have to parse all the header files first and keep a table of all the instance methods so that it only passes "this" in instance methods. Getting this working properly is dependent on getting the trace tool to parse all the header files successfully, a lot of which are currently excluded in Exclusions.java.

> Improve trace readability
> -------------------------
>
>          Key: AXISCPP-165
>          URL: http://issues.apache.org/jira/browse/AXISCPP-165
>      Project: Axis-C++
>         Type: Improvement
>   Components: Basic Architecture
>     Reporter: Mark Whitlock
>     Assignee: Mark Whitlock
>     Priority: Minor

>
> The readability of entry/exit trace could be improved by ...
>  - making each trace statement one line instead of about 4 lines
>  - removing unnecessary data such as the filename and linenumber since these can be known from the classname and methodname
>  - indentation reflecting the call depth. This would make it easier to visually match up an entry with its corresponding exit when viewing the trace file. Maybe braces could be used since the % command in vi matches braces.
> Also for instance methods, the address of the instance would be very useful on a trace entry appearing in the trace file. For multithreaded applications the thread id would also be useful. I guess there are other things that might be traced once only when trace is initialised, like all the environment variables, the current working directory, the current userid and groupid, the datestamp/size/build number of the various libraries, etc.

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