[
https://issues.apache.org/jira/browse/QPID-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492294
]
Alan Conway commented on QPID-154:
----------------------------------
When complete, update daemon quit/kill tests to verify from logs that daemon
was shut down correctly.
> Logging/tracing for C++.
> ------------------------
>
> Key: QPID-154
> URL: https://issues.apache.org/jira/browse/QPID-154
> Project: Qpid
> Issue Type: New Feature
> Components: C++ Broker, C++ Client
> Affects Versions: M2
> Reporter: Alan Conway
> Assigned To: Alan Conway
>
> Qpid needs logging infrastructure for user logging and debug tracing.
> Performance is critical, in particular the descision *not* to log a disabled
> messages must be extremely cheap so that disabled logging statements have no
> significant performance impact.
> Ideally a single system for both user logging and debug tracing so that debug
> tracing can be left in release builds and enabled to diagnose problems in
> the users's environment.
> Only if we can't get acceptable performance should we consider a separate
> debug tracing facility that is compiled out of release builds for tracing
> critical code.
> Highly desirable to use an existing open source solution rather than reinvent
> the wheel provided we can find one that is acceptable, need some research &
> discussion on dev list before selecting and implementing.
> Having the file/line in exception messages (as qpid does currently) is
> valuable, qpid::Exception should take a srcline parameter.
> Low-level tracing should provide function entry-exit logging via a
> macro+guard object that logs in constructor/destructor. (note
> BOOST_FUNCTION_NAME gives the current function name in a macro)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
