linphone-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-developers] New linphone crashes on Arch Linux


From: Guillaume Beraudo
Subject: Re: [Linphone-developers] New linphone crashes on Arch Linux
Date: Fri, 28 Mar 2014 15:36:38 +0100
User-agent: Mutt/1.5.23 (2014-03-12)

Clearly, there is a malformed call log that makes linphone crash.

The logs are in .linphonerc. Do you see something strange there?

You may also send me the log part of your .linphonerc and I will
investigate it.

Cheers,

Guillaume

On Fri, Mar 28, 2014 at 05:04:34PM +0300, igpg wrote:
> Here we go bt & bt full,
> 
> Using host libthread_db library "/usr/lib/libthread_db.so.1".
> Core was generated by `linphone'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  0x00007f643cbfdb71 in belle_sip_object_marshal () from
> /usr/lib/libbellesip.so.0
> warning: File "/usr/lib/libstdc++.so.6.0.19-gdb.py" auto-loading has
> been declined by your `auto-load safe-path' set to
> "$debugdir:$datadir/auto-load".
> To enable execution of this file add
>     add-auto-load-safe-path /usr/lib/libstdc++.so.6.0.19-gdb.py
> line to your configuration file "/home/arch/.gdbinit".
> To completely disable this security protection add
>     set auto-load safe-path /
> line to your configuration file "/home/arch/.gdbinit".
> For more information about this security protection see the
> "Auto-loading safe path" section in the GDB manual.  E.g., run from the
> shell:
>     info "(gdb)Auto-loading safe path"
> (gdb) bt
> #0  0x00007f643cbfdb71 in belle_sip_object_marshal () from
> /usr/lib/libbellesip.so.0
> #1  0x00007f643f04d53e in sal_address_as_string () from
> /usr/lib/liblinphone.so.6
> #2  0x0000000000425e01 in linphone_gtk_call_log_update ()
> #3  0x000000000041a6b2 in ?? ()
> #4  0x00007f643f02a41d in linphone_configuring_terminated () from
> /usr/lib/liblinphone.so.6
> #5  0x00007f643f02ac28 in linphone_core_new_with_config () from
> /usr/lib/liblinphone.so.6
> #6  0x0000000000416b8f in main ()
> (gdb) bt full
> #0  0x00007f643cbfdb71 in belle_sip_object_marshal () from
> /usr/lib/libbellesip.so.0
> No symbol table info available.
> #1  0x00007f643f04d53e in sal_address_as_string () from
> /usr/lib/liblinphone.so.6
> No symbol table info available.
> #2  0x0000000000425e01 in linphone_gtk_call_log_update ()
> No symbol table info available.
> #3  0x000000000041a6b2 in ?? ()
> No symbol table info available.
> #4  0x00007f643f02a41d in linphone_configuring_terminated () from
> /usr/lib/liblinphone.so.6
> No symbol table info available.
> #5  0x00007f643f02ac28 in linphone_core_new_with_config () from
> /usr/lib/liblinphone.so.6
> No symbol table info available.
> #6  0x0000000000416b8f in main ()
> No symbol table info available.
> (gdb)
> 
> Thanks.
> 
> On 03/28/14 16:19, Guillaume Beraudo wrote:
> > Hi,
> >
> > Type "ulimit -c unlimited"
> > Then "linphone"
> >
> > It will crash and create a "core" file.
> > Type "gdb linphone core"
> > Then "bt".
> > Copy paste what is shown.
> >
> > Guillaume
> >
> > On Fri, Mar 28, 2014 at 04:11:43PM +0300, igpg wrote:
> >> Hi,
> >>
> >> attaching the strace , no idea though what's triggering the crash,
> >> please specify where I can find the content and I will send the file.
> >>
> >> Thanks.
> >>
> >> On 03/28/14 15:52, Guillaume Beraudo wrote:
> >>> Hi,
> >>>
> >>> You have some error parsing something.
> >>> Please send a stack trace and the content which is triggering the crash.
> >>>
> >>>
> >>> Guillaume
> >>>
> >
> >> _______________________________________________
> >> 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
> 
> 
> 
> _______________________________________________
> Linphone-developers mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/linphone-developers



reply via email to

[Prev in Thread] Current Thread [Next in Thread]