[DISPATCH-1615] Backtrace of leaked allocations does not show object address

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.12.0
• Component/s: Container
• Assignee: Charles E. Rolke
• Reporter: Charles E. Rolke
• Created: 06/Apr/20 15:41
• Updated: 30/Apr/20 21:44
• Resolved: 07/Apr/20 13:17

Description

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

Issue Links

• links to: GitHub Pull Request #715