Re: [Linphone-developers] Possible bug in Linphone

[Boštjan Vesnicer]

Hi,

sorry for my late response. Here is the gdb backtrace. I hope it helps.

Best regards,
Bostjan

(gdb) run
Starting program: linphonec
[Thread debugging using libthread_db enabled]
c[New Thread 0xb3fd7b70 (LWP 8238)]
[Thread 0xb3fd7b70 (LWP 8238) exited]
[New Thread 0xb3fd7b70 (LWP 8239)]
ALSA lib conf.c:4630:(snd_config_expand) Unknown parameters 0
ALSA lib control.c:882:(snd_ctl_open_noupdate) Invalid CTL default:0
ALSA lib conf.c:4630:(snd_config_expand) Unknown parameters 0
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM default:0
ALSA lib conf.c:4630:(snd_config_expand) Unknown parameters 0
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM default:0
[Thread 0xb3fd7b70 (LWP 8239) exited]
[New Thread 0xb3fd7b70 (LWP 8240)]
[New Thread 0xb37d6b70 (LWP 8241)]
Ready
Warning: video is disabled in linphonec, use -V or -C or -D to enable.
linphonec> call sip:192.168.[Thread 0xb37d6b70 (LWP 8241) exited]
[New Thread 0xb37d6b70 (LWP 8242)]
0.137
Establishing call id to <sip:192.168.0.137>, assigned id 1
linphonec> Contacting <sip:192.168.0.137>
linphonec> Call 1 to <sip:192.168.0.137> in progress.
Remote ringing.
linphonec> [New Thread 0xb2dd3b70 (LWP 8243)]
Remote ringing...
linphonec> Call 1 to <sip:192.168.0.137> ringing.

Program received signal SIGSEGV, Segmentation fault.
0x0026e3b0 in osip_list_eol (li=0x58, i=0) at osip_list.c:93
93              if (i < li->nb_elt)
(gdb) bt
#0  0x0026e3b0 in osip_list_eol (li=0x58, i=0) at osip_list.c:93
#1  0x00149856 in _osip_list_set_empty (l=0x58, freefunc=0x271930
<osip_contact_free>) at sal_eXosip2.c:33
#2  0x0014c7d3 in call_accepted (sal=0x8097300) at sal_eXosip2.c:1063
#3  process_event (sal=0x8097300) at sal_eXosip2.c:1715
#4  sal_iterate (sal=0x8097300) at sal_eXosip2.c:1845
#5  0x00142aac in linphone_core_iterate (lc=0x806a7e8) at linphonecore.c:1674
#6  0x0804d0a6 in linphonec_idle_call () at linphonec.c:982
#7  0x0018915a in rl_read_key () from /lib/libreadline.so.6
#8  0x00172d3e in readline_internal_char () from /lib/libreadline.so.6
#9  0x001732ad in readline () from /lib/libreadline.so.6
#10 0x0804d2d0 in linphonec_readline (prompt=0x8059c60 "linphonec> ")
at linphonec.c:546
#11 0x0804d807 in linphonec_main_loop (argc=1, argv=0xbffff304) at
linphonec.c:1091
#12 main (argc=1, argv=0xbffff304) at linphonec.c:633




On Mon, May 16, 2011 at 10:34 PM, Simon Morlat
<address@hidden> wrote:
> Hi,
>
> Yes, a log or a gdb backtrace would be helpful.
>
> SImon
>
> Le samedi 30 avril 2011 à 17:29 +0200, Boštjan Vesnicer a écrit :
>> Hi,
>>
>> I think I found a subtle bug in Linphone. Here is a pseudo code, which
>> shows how to reproduce it:
>>
>> while TRUE
>> do
>>   A calls B
>>   B accepts a call, but hangs up immediately
>> end
>>
>> After some random number (usually between 1 and 5) of trials, A crashes.
>>
>> In the test case, A was a Linphone 3.4.3 client and B was a simple SIP
>> client based on the liblinphone library. I can provide further info if
>> needed.
>>
>> Best regards,
>>
>> Bostjan
>>
>> _______________________________________________
>> Linphone-developers mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/linphone-developers
>
>
>
> _______________________________________________
> Linphone-developers mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/linphone-developers
>