<div dir="ltr"><div><div><div>Hi Razvan!<br><br></div>Thanks for the hint, but the memory dump logged more than 174000 lines. The zipped file is 1 MB big (18 MB unzipped) and a free account on pastebin won´t let me paste a file bigger than 500 KB.<br>
<br></div>Is there any email I can sent it privately, or could you give us any guidance on how to analyse that info and get to any conclusion? <br><br>Thanks and sorry for the huge dump...<br><br></div>Mariana.<br></div>
<div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Apr 22, 2013 at 9:08 AM, Răzvan Crainea <span dir="ltr"><<a href="mailto:razvan@opensips.org" target="_blank">razvan@opensips.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi, Mariana!<br>
<br>
Please upload the files on one of the online file storage services (like [1]), and paste the links here.<br>
<br>
[1] <a href="http://pastebin.com/" target="_blank">http://pastebin.com/</a><br>
<br>
Best regards,<br>
<br>
Razvan Crainea<br>
OpenSIPS Core Developer<br>
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.<u></u>com</a><div><div class="h5"><br>
<br>
On 04/22/2013 01:58 PM, Mariana Arduini wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
Hello all!<br>
<br>
We are running a suite of automated tests using Opensips 1.8.1.<br>
<br>
Once in a while, we get this crash, apparently related to a call where<br>
we have to update Session Timers. To try to get more info, we did this:<br>
<br>
- started opensips with Valgrind: valgrind --leak-check=full<br>
--show-reachable=yes --tool=memcheck --track-origins=yes<br>
/usr/local/sbin/opensips -P /var/run/opensips.pid -f<br>
/usr/local/etc/opensips/<u></u>opensips.cfg -m 64 2> valgrind.output<br>
- in the Makefile.conf, we enabled DEFS+= -DDBG_F_MALLOC and disabled<br>
DEFS+= -DF_MALLOC<br>
- in opensips.cfg file, we added lines: memlog=6 and memdump=1<br>
<br>
At some point in the tests, process 60939 exited with signal 11. A core<br>
was not generated, but we could get some info from Valgrind, and also<br>
the dump in syslog file.<br>
<br>
I´ve attached a file containning the syslog and valgrind report to this<br>
same message 3 days ago, but it was bigger than the max 40KB and I guess<br>
the monitoring blocked it. Please let me know one email address I can<br>
sent it to.<br>
<br>
Hopefully you can help us to detect what may be corrupting the memory.<br>
<br>
Thanks!<br>
Mariana.<br>
<br>
<br></div></div>
______________________________<u></u>_________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-<u></u>bin/mailman/listinfo/users</a><br>
<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-<u></u>bin/mailman/listinfo/users</a><br>
</blockquote></div><br></div>