Valgrind Output of Failed Port Binding reveals lost blocks

Added by Christian Meyer about 2 months ago

Hi there,

I am trying to figure out some weird stuff:
Some of my Modules mess with my Application and throw on Session Timeout (free() invalid Pointer, or double free())
Debugging the stack trace places the exception somewhere in the destructor for Widget, expecially the deletion of EventBaseSignal vector.

Running Valgrind by accident while another debugging session was active on the same Ports gave this output

Valgrind Complete Log

With this Summary:

==29806== HEAP SUMMARY:
==29806==     in use at exit: 53,834 bytes in 271 blocks
==29806==   total heap usage: 24,296 allocs, 24,033 frees, 2,185,561 bytes allocated
==29806== LEAK SUMMARY:
==29806==    definitely lost: 3,190 bytes in 8 blocks
==29806==    indirectly lost: 0 bytes in 0 blocks
==29806==      possibly lost: 0 bytes in 0 blocks
==29806==    still reachable: 48,628 bytes in 242 blocks
==29806==         suppressed: 0 bytes in 0 blocks
==29806== Rerun with --leak-check=full to see details of leaked memory
==29806== For lists of detected and suppressed errors, rerun with: -s
==29806== ERROR SUMMARY: 28 errors from 3 contexts (suppressed: 0 from 0)

I don't think that is supposed to happen?

I have no experience with valgrind so I can only guess how output like that is helping, but it messes with my problem search =/