axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian Dick (JIRA)" <>
Subject [jira] Closed: (AXISCPP-165) Improve trace readability
Date Mon, 03 Apr 2006 09:03:47 GMT
     [ ]
Adrian Dick closed AXISCPP-165:

> Improve trace readability
> -------------------------
>          Key: AXISCPP-165
>          URL:
>      Project: Axis-C++
>         Type: Improvement

>   Components: Trace Utility
>     Reporter: Mark Whitlock
>     Assignee: Mark Whitlock
>     Priority: Minor
>      Fix For: 1.5 Alpha

> 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:
For more information on JIRA, see:

View raw message