You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Charles E. Rolke (Jira)" <ji...@apache.org> on 2020/04/06 15:42:00 UTC

[jira] [Created] (DISPATCH-1615) Backtrace of leaked allocations does not show object address

Charles E. Rolke created DISPATCH-1615:
------------------------------------------

             Summary: Backtrace of leaked allocations does not show object address
                 Key: DISPATCH-1615
                 URL: https://issues.apache.org/jira/browse/DISPATCH-1615
             Project: Qpid Dispatch
          Issue Type: Improvement
          Components: Container
            Reporter: Charles E. Rolke
            Assignee: Charles E. Rolke


Also, in the event of hundreds of leaked objects the debug log requires a program to reconstruct the details into legible form.

This patch would replace the timestamp line with a CSV line that would identify the object. The fields are:
 * "Leak" - literal word for grepping
 * debug_dump file name - identifies which router
 * timestamp
 * address of leaked object

Then when a log file reveals the address of an object it may be more precisely linked to the leaks.

For instance:

{{Leak,/home/qpid-dispatch/build/tests/system_test.dir/system_tests_policy/someTest/setUpClass/INT.B-qddebug.txt,2020-04-06 09:55:56.968527 -0400,qd_link_ref_t,0x15149d0}}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org