[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Linphone-users] Segfault after "No listening point matching" error
From: |
Christian Spielberger |
Subject: |
[Linphone-users] Segfault after "No listening point matching" error |
Date: |
Thu, 28 Apr 2016 17:04:03 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Hello,
after the errors "No listening point matching" and "no channel available" which
are printed somewhere in sal_call(call->op,from,real_url) there occurs a
segfault in line
linphonecore.c:3081
...
call->log->call_id=ms_strdup(sal_op_get_call_id(call->op)); /*must be known at
that time*/
...
because call->op is already NULL after the return of sal_call. I found that
the linphone_call_set_released and sal_op_release is called somewhere in
sal_call, if the above error arises. And sal_call returns with err==-1.
What could be done against the segfault? Maybe the "if (err<0)" check should be
done directly after returning from sal_call. But in this case also the "err<0"
path is wrong. Both lines
linphone_call_stop_media_streams(call);
linphone_call_set_state(call,LinphoneCallError,"Call failed");
are crashing with a segfault in this error situation. Remove them both?
Code base:
---
commit f10471de2e2316958ccce54a2dbcde41cd9bb05f
Author: Gautier Pelloux-Prayer <address@hidden>
Date: Thu Apr 28 14:28:18 2016 +0200
player_tester.c: fix test on io
---
regards,
Christian Spielberger.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Linphone-users] Segfault after "No listening point matching" error,
Christian Spielberger <=