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-182) Entry/exit trace causes code bloat
Date Fri, 12 Nov 2004 14:21:25 GMT
     [ ]
Mark Whitlock closed AXISCPP-182:

     Resolution: Fixed
    Fix Version: 1.4 Alpha


> Entry/exit trace causes code bloat
> ----------------------------------
>          Key: AXISCPP-182
>          URL:
>      Project: Axis-C++
>         Type: Bug
>   Components: Basic Architecture
>     Reporter: Mark Whitlock
>     Assignee: Mark Whitlock
>     Priority: Minor
>      Fix For: 1.4 Alpha

> The trace tool generates code that constructs and concatenates 
> strings from parameters, and puts it within a try/catch. This code
> will get more complicated when full parameter tracing is done. This
> works OK, except that much of this code is repeated many times 
> throughout Axis C++ as the trace tool adds similar code to all 
> methods. This repetition makes the size of the built libraries 
> larger and so the footprint of Axis C++ bigger. This code could 
> be put inside the trace class itself by passing in (for instance)
> a variable parameter list containing the parameters, the names
> of the parameters, their datatypes and their lengths. Then the
> trace class could do the string manipulation. Also the trace
> class could contain the try/catch instead of the generated code.
> I haven't investigated how much bigger the traced libraries are,
> so I don't know how important a problem this is.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message