New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
linphonec coredumps when answering calls #27
Comments
I am also having a very similar issue. Could this be due to misconfigured media codecs?
|
Hi! I am seeing the same segfault with the latest 3.12.0 version. Could this issue to be reopened? |
The segfault also happens when autoanswer is enabled. |
Here is a little patch that should solve this issue. Perhaps someone with right to patch can do this?
|
Thanks @uli7. I do not have the rights to commit this patch. Hopefully this gets accepted soon. |
Yes you are right - the comment is somehow obsolete now :-D |
Hi
I have tried to compile the latest version 3.11.2 from the master branch and calling out works fine, but when I am trying to answer calls the linphonec process core dumps. The linphone application works fine, but the commandline version does not handle incoming calls at all.
I have not compiled with debug info but got the following backtrace in gdb from the generated core file:
Core was generated by `./linphonec -d 6 -l /home/velferd/bin/log.txt'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fdc9d265a94 in linphone_call_accept_with_params () from /home/velferd/linphone-desktop/OUTPUT/desktop/lib/liblinphone.so.9
[Current thread is 1 (Thread 0x7fdc9d6d7740 (LWP 19166))]
(gdb) bt
#0 0x00007fdc9d265a94 in linphone_call_accept_with_params () from /home/velferd/linphone-desktop/OUTPUT/desktop/lib/liblinphone.so.9
#1 0x0000563c5ab76532 in lpc_cmd_answer ()
#2 0x0000563c5ab7715e in linphonec_parse_command_line ()
#3 0x0000563c5ab71327 in main ()
(gdb) quit
There is also a post of the same problem here:
https://lists.gnu.org/archive/html/linphone-developers/2017-05/msg00007.html
Does anyone have a workaround for this issue or could someone patch the master branch to fix it?
I rolled back to version 3.11.1-192-g2a4a17bff and everything is working like a charm there!
Best Regards,
Tomas
The text was updated successfully, but these errors were encountered: