[OpenSIPS-Devel] Help need to understand the memory log

[Liviu Chircu]

Hi Surya,

     * Every memory line you see there is **unfreed** memory. 
Overwhelmingly too many entries in some situations could point to a mem 
leak.
     * Regarding the three patterns, if you spot *any* broken pattern, 
then you've ran into a corrupted (overwritten) block.

Best regards,

Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com

On 13.10.2015 19:23, surya wrote:
> Hi Răzvan,
>
> Thanks for the response.
>
> I am sorry but I still did not understood. I understand that the memory is
> allocated by some function at some line but how do I know it got freed? I
> also want to understand what does used=1 means and does this line *start
> check=f0f0f0f0, end check= c0c0c0c0, abcdefed* has any significance in
> investigation.
>
> Thanks & Regards,
> Surya
>
>
>
> --
> View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Help-needed-to-understand-the-memory-log-tp7599422p7599447.html
> Sent from the OpenSIPS - Devel mailing list archive at Nabble.com.
>
> _______________________________________________
> Devel mailing list
> Devel at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/devel/attachments/20151013/504acffe/attachment.htm>