Program takes 5 seconds to terminate. Tool for debugging?

Question

I created a tool using Opensplice DDS 6.7 to create a reader, wait for the callback to execute on the read message, and print the value of the message. We use Google Protobuf for our message structures. After printing the value of the message and executing return 0;, the program takes nearly 5 seconds to actually terminate.

Stepping through GDB shows many calls to destructors in Protobuf and thread joins from opensplice. Is there a unix tool or GDB tool to analyze wall clock execution time of threads/functions or number of times a function is called to help narrow down which library, or the wrapper, is causing the hang on destruction?

Compiling with -O3 makes no discernable difference on this behavior. I'm debugging without optimization so I can see the symbols but the same thing happens when the program is optimized. — Bobby Tables, Aug 30 '21 at 16:43
Run under strace and see if there are system calls where the program hangs. — n. m. could be an AI, Aug 30 '21 at 17:13
Thanks! This is exactly what I was looking for, feel free to make an answer and I'll accept. Something is calling sleep for a long time and using GDB I narrowed down which threads are the last to join. — Bobby Tables, Aug 30 '21 at 17:24

score 0 · Answer 1 · answered Aug 31 '21 at 22:40

Strace was the tool I was looking for. Helped identify what was happening during destruction to reveal one of the threads for opensplice was sleeping for ~5 seconds before terminating. Eventually found the issue was using the system opensplice config rather than the one setup for the application. After switching which opensplice config was used, the program terminates quickly and gracefully.

Program takes 5 seconds to terminate. Tool for debugging?

1 Answers1