<p>Regarding the troubleshooting with gdb, the idea is to print all chunks of memory if you didn't get the <code>qm_status</code> log messages.</p>
<p>The wiki has some gdb scripts at:</p>
<ul>
<li><a href="https://www.kamailio.org/wiki/tutorials/troubleshooting/memory#using_gdb">https://www.kamailio.org/wiki/tutorials/troubleshooting/memory#using_gdb</a></li>
</ul>
<p>But they are for pkg as they use <code>mem_block</code> and the issue here seems to be in shm, so you have to use <code>shm_block</code> instead of <code>mem_block</code>.</p>
<p>The target is to find the fragment before the one that has the beginning overwritten, listed in the log message:</p>
<pre><code>Mar  9 10:33:49 kamserv /usr/local/sbin/kamailio[2945]: : <core> [mem/q_malloc.c:140]: qm_debug_frag(): BUG: qm_*: fragm. 0x7f064ea52480 (address 0x7f064ea524b0) beginning overwritten(646e756f622d6575)!
</code></pre>
<p>Probably you can adjust the gdb scripts in order to print first only the addresses for fragments, then print the content of the fragment before the one overwritten.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/kamailio/kamailio/issues/1026#issuecomment-285496870">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AF36ZdToxjlG1SDC1G6p0HkaxQalkef2ks5rkHYPgaJpZM4MX6sv">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AF36ZbeYGP4gaofHaSE6Cf--mcHd-RHSks5rkHYPgaJpZM4MX6sv.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/kamailio/kamailio/issues/1026#issuecomment-285496870"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/kamailio/kamailio","title":"kamailio/kamailio","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/kamailio/kamailio"}},"updates":{"snippets":[{"icon":"PERSON","message":"@miconda in #1026: Regarding the troubleshooting with gdb, the idea is to print all chunks of memory if you didn't get the `qm_status` log messages.\r\n\r\nThe wiki has some gdb scripts at:\r\n\r\n  * https://www.kamailio.org/wiki/tutorials/troubleshooting/memory#using_gdb\r\n\r\nBut they are for pkg as they use `mem_block` and the issue here seems to be in shm, so you have to use `shm_block` instead of `mem_block`.\r\n\r\nThe target is to find the fragment before the one that has the beginning overwritten, listed in the log message:\r\n\r\n```\r\nMar  9 10:33:49 kamserv /usr/local/sbin/kamailio[2945]: : \u003ccore\u003e [mem/q_malloc.c:140]: qm_debug_frag(): BUG: qm_*: fragm. 0x7f064ea52480 (address 0x7f064ea524b0) beginning overwritten(646e756f622d6575)!\r\n```\r\n\r\nProbably you can adjust the gdb scripts in order to print first only the addresses for fragments, then print the content of the fragment before the one overwritten.\r\n"}],"action":{"name":"View Issue","url":"https://github.com/kamailio/kamailio/issues/1026#issuecomment-285496870"}}}</script>