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 "Mark Whitlock (JIRA)" <ax...@ws.apache.org> on 2004/11/12 15:21:25 UTC
[jira] Closed: (AXISCPP-182) Entry/exit trace causes code bloat
[ http://nagoya.apache.org/jira/browse/AXISCPP-182?page=history ]
Mark Whitlock closed AXISCPP-182:
---------------------------------
Resolution: Fixed
Fix Version: 1.4 Alpha
Fixed
> Entry/exit trace causes code bloat
> ----------------------------------
>
> Key: AXISCPP-182
> URL: http://nagoya.apache.org/jira/browse/AXISCPP-182
> 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:
http://nagoya.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