Not a core dump that is helpful:<div><br></div><div><div>Core was generated by `asterisk'.</div><div>Program terminated with signal 11, Segmentation fault.</div><div>#0 0x0000000801e62828 in ?? ()</div><div>(gdb) bt</div>
<div>#0 0x0000000801e62828 in ?? ()</div><div>#1 0x0000000000000001 in ?? ()</div><div>#2 0x00000008030e9d90 in ?? ()</div><div>#3 0x000000000000002e in ?? ()</div><div>#4 0x000000080101b6e3 in ?? ()</div><div>#5 0x000000000000007e in ?? ()</div>
<div>#6 0x000000000048dd28 in ast_get_srv ()</div><div>Cannot access memory at address 0x7ffffeb6ac18</div><div>(gdb) quit </div><div><br></div><div><br></div><div>I'm sure it will core dump over night and I'll get that one, unless leaving the debug symbols in fixes it. :-)</div>
<div><br></div><div>-Chris</div><br><div class="gmail_quote">On Mon, Feb 15, 2010 at 9:52 PM, Max Khon <span dir="ltr"><<a href="mailto:fjoe@samodelkin.net">fjoe@samodelkin.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello, Chris!<br><br><div class="gmail_quote"><div><div></div><div class="h5">On Tue, Feb 16, 2010 at 5:12 AM, Chris Coleman <span dir="ltr"><<a href="mailto:chrisc@vmunix.com" target="_blank">chrisc@vmunix.com</a>></span> wrote:<br>
<div> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
<span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse"><div>I'm running Asterisk on FBSD 7.2 using only SIP incoming DIDs. I'm also using unixODBC to connect to a postgres DB. I'm running asterisk from ports.</div>
<div><br></div><div>Here is my system info:</div><div><br></div><div>Asterisk 1.4.26.2, Copyright (C) 1999 - 2008 Digium, Inc. and others.</div><div><br></div><div><div>FreeBSD kvm10.podlinez.lan 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4 #0: Fri Oct 2 08:22:32 UTC 2009 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64</div>
<div><br></div><div><br></div><div>I'm getting very frequent core dumps, so I've rebuilt asterisk with -g3 to enable debug. I've also ran it with valgrind and attached it to the e-mail.</div></div><div><br></div>
Here is the Summary:<div><br></div><div><div>==30746== definitely lost: 28,597 bytes in 75 blocks</div><div>==30746== indirectly lost: 143,559 bytes in 308 blocks</div><div>==30746== possibly lost: 6,119,992 bytes in 98,335 blocks</div>
<div>==30746== still reachable: 3,169,594 bytes in 37,091 blocks</div><div>==30746== suppressed: 0 bytes in 0 blocks</div><div><br></div><div>It seems like it has a memory leak that is causing the problem.</div>
<div><br></div><div>In my experience, it dies trying to do a DB call.</div></div></span></blockquote></div></div><div><br>The leak does not seem to be big enough to cause any problems. Do you have a core files and can you show the stack trace?<br>
<br>Max <br><br></div></div>
</blockquote></div><br><br clear="all"><br>-- <br>Chris Coleman -- http://Podlinez.com<br>
</div>