Are you updating with "make current" each time?<br><br><br><div class="gmail_quote">On Fri, Mar 27, 2009 at 2:58 AM, Jason White <span dir="ltr"><<a href="mailto:jason@jasonjgw.net">jason@jasonjgw.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">While I was trying to obtain more detailed logs of my portaudio problems,<br>
FreeSWITCH crashed, leaving a core file.<br>
<br>
The backtraces are here:<br>
<a href="http://pastebin.freeswitch.org/7998" target="_blank">http://pastebin.freeswitch.org/7998</a><br>
<br>
As far as I can remember, at the time of the segfault, one channel was trying<br>
to connect and not succeeding; I had just issued a pa hangup command on it and<br>
then a pa call to try connecting again. Since my memory of exactly what was<br>
happening isn't as reliable as it should be, the value of the backtraces may<br>
be diminished.<br>
<br>
As to the portaudio problem, with rev. 12701 (Debian Sid, kernel 2.6.29,<br>
x86_64 architecture), the situation appears to be that the second and<br>
subsequent concurrent portaudio calls sometimes wait for a long time after<br>
issuing a log message such as the following:<br>
<br>
[NOTICE] switch_channel.c:597 switch_channel_set_name() New Channel<br>
sofia/internal/<a href="http://1000@192.168.0.2:5070" target="_blank">1000@192.168.0.2:5070</a> [d6e56642-1a9b-11de-b23e-c5a9450df57d]<br>
<br>
These calls do not always complete successfully, but I'm still trying to<br>
collect more precise details of when and why they fail.<br>
<br>
With apologies for being unable to use Jira, if anything valuable appears in<br>
the backtraces, you are welcome to let me know via the list or by e-mail.<br>
<br>
I have previously seen crashes while working with multiple portaudio calls,<br>
but I don't yet have a reliable means to reproduce them.<br>
<br>
If the backtraces are revealing, that's good, but if not, that's fine too and<br>
I'll collect better particulars next time.<br>
<div><div></div><div class="h5"><br>
<br>
_______________________________________________<br>
Freeswitch-users mailing list<br>
<a href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
<br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="http://iax:guest@conference.freeswitch.org/888">iax:guest@conference.freeswitch.org/888</a><br>
<a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>pstn:213-799-1400<br>