Bug#1021576: linphone-desktop: Core dumped: Program terminated with signal SIGABRT, Aborted.

[ael]

> > Severity: normal
> >
> > After updating to linphone-common:all 5.0.37-6 and liblinphone10:amd64 5.0.37-6
> > as part of routine testing updates, I find that /usr/bin/linphone from
> > linphone-desktop aborts and dumps core as of today.
> >
> > Reportbug highlighted linphone-desktop_4.3.2-2+b1_amd64.deb
> > in unstable. Trying to install that failed on a depedency on
> > libqt5qml5_5.15.6+dfsg-2_amd64.deb
> >
> > Trying to install those broke again on a dependency on qtdeclarative-abi-5-15-6
> > which does not appear to exist.
> 
> The qtbase-abi-5-15-6 transition is still on-going[0], so any 5-15-6
> packages should not be installed yet.  You must downgrade any you have
> installed back to 5-15-4.

Thanks for the quick reply.

I had already downgraded back to 5-15-4. As noted above I tried to
use the unstable packages, and got a partial upgrade as you
gathered. I had alraedy cleaned out those packages and confirmed that
linphone still crashed.

> 
> > So linphone is broken on testing.
> >
> > $gdb -c core
> > does help much probably because I have set ulimit too small, and right
> > now I can't remember where ulimit gets set.

I have since increased unlimit, but gdb -c core gives the same lack of
information.

> > But it ends with
> > Core was generated by `linphone'.
> > Program terminated with signal SIGABRT, Aborted.
> 
> Did you maybe forget to attach some files before sending this message?
> I ask because your bug report is very light on details.  You only say
> that 5.0.37-6 crashes with SIGABRT, but not what version you used
> before and where it crashes.

Indeed. I was surprised that gdb gave so little information.
I was sure that I had linphone-desktop-dbgsym installed, but
somehow it was not present. Now installed, but gdb -c core still
not giving anything useful. I may need to install further -dbgsym
packages.

It does say "failed to read a valid object file image from memory".


>You don't provide any stderr output or
> logs either.  And if you have gdb installed and your APT preferences
> are on testing-debug you are clearly skilled enough to install -dbgsym
> packages and provide a stack backtrace.  I currently have no
> information I can work with.

Understood. I don't use gdb very often, so will need to refresh my
memory. This is a just a quick response untill I have time to
explore further.

But I emphasize that I just did my routine (normally daily)
apt-get upgrade and apt-get dist-upgrade, and that broke linphone.
I can't remember when I last used linphone, but it was within a few
days.

Hope to report much more soon...