Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
How should we enable the debug information when Kamailio is compiled from source please?
At the moment running valgrind on a test system we get an output like the one below.
==3246448== HEAP SUMMARY:
==3246448== in use at exit: 9,225,711 bytes in 293 blocks
==3246448== total heap usage: 4,020 allocs, 3,727 frees, 9,833,603 bytes allocated
==3246448==
==3246448== LEAK SUMMARY:
==3246448== definitely lost: 0 bytes in 0 blocks
==3246448== indirectly lost: 0 bytes in 0 blocks
==3246448== possibly lost: 0 bytes in 0 blocks
==3246448== still reachable: 9,225,711 bytes in 293 blocks
==3246448== suppressed: 0 bytes in 0 blocks
==3246448== Rerun with --leak-check=full to see details of leaked memory
==3246448==
==3246448== For lists of detected and suppressed errors, rerun with: -s
==3246448== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==3246474== Invalid read of size 8
==3246474== at 0x5A89590: Perl__invlist_intersection_maybe_complement_2nd (in /usr/lib/x86_64-linux-gnu/libperl.so.5.30.0)
==3246474== by 0x5A89BD4: ??? (in /usr/lib/x86_64-linux-gnu/libperl.so.5.30.0)
==3246474== by 0x5A99C7E: ??? (in /usr/lib/x86_64-linux-gnu/libperl.so.5.30.0)
==3246474== by 0x5AA0267: ??? (in /usr/lib/x86_64-linux-gnu/libperl.so.5.30.0)
==3246474== by 0x5AA4D02: ??? (in /usr/lib/x86_64-linux-gnu/libperl.so.5.30.0)
==3246474== by 0x5AA52CE: ??? (in /usr/lib/x86_64-linux-gnu/libperl.so.5.30.0)
==3246474== by 0x5AA0086: ??? (in /usr/lib/x86_64-linux-gnu/libperl.so.5.30.0)
==3246474== by 0x5AA4D02: ??? (in /usr/lib/x86_64-linux-gnu/libperl.so.5.30.0)
==3246474== by 0x5AA52CE: ??? (in /usr/lib/x86_64-linux-gnu/libperl.so.5.30.0)
==3246474== by 0x5AAA36B: Perl_re_op_compile (in /usr/lib/x86_64-linux-gnu/libperl.so.5.30.0)
==3246474== by 0x5A3EC34: Perl_pmruntime (in /usr/lib/x86_64-linux-gnu/libperl.so.5.30.0)
==3246474== by 0x5A7B23A: Perl_yyparse (in /usr/lib/x86_64-linux-gnu/libperl.so.5.30.0)
...etc..
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.