axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Whitlock (JIRA)" <>
Subject [jira] Closed: (AXISCPP-406) Make AxisTrace work better with TraceAnalyzer
Date Mon, 04 Jul 2005 15:09:10 GMT
     [ ]
Mark Whitlock closed AXISCPP-406:

    Resolution: Fixed

All the problems reported in this JIRA have now been fixed except for multiline output AXISCPP-728
and throw out trace AXISCPP-729 for which separate JIRAs have now been raised.

> Make AxisTrace work better with TraceAnalyzer
> ---------------------------------------------
>          Key: AXISCPP-406
>          URL:
>      Project: Axis-C++
>         Type: Bug
>   Components: Trace Utility
>     Versions: 1.5 Alpha
>     Reporter: Mark Whitlock
>     Assignee: Mark Whitlock
>     Priority: Minor

> I have formatted axis trace so that it is compatible with the free trace analyzer available
from However there are some unresolved issues. There
>  - the timestamp on every line does not include milliseconds because struct tm does not
support milliseconds. This might require platform specific functions. Timestamps without milliseconds
don't make much sense since many calls happen in every second.
>  - the environment variable section at the top of the trace easily blew the tool's limit.
When there was too much data in that section, the tool failed to read in the trace file.
>  - The thread id is not output in the trace because the client library is not currently
linked with pthreads (it should be).
>  - Character strings that contain newline characters are split over several lines in
the trace. This is OK, but it looks a little odd. I can't think of a better solution.
>  - Object ids (value of the this pointer) appears in the trace, but are they output so
that the tool can show all methods acting on a particular instance of a particular class.

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