Segfault error in debian testing (Jessie)

Submitted by canselleiro on Mon, 2014-03-10 21:18

Forums:

Hi everyone,
today I update the packages in debian testing (amd64) and MOC updated to 2.5.0~beta2-1 version.

Now when I try to start the MOC session it fails with a segfault error without more info (--debug yields same result):
$ mocp
Fallo de segmento # segment fault, in english
$ echo $?
139

In the syslog appears:
mocp[11405]: segfault at 0 ip 00007f2eeff3f0b6 sp 00007fff74b11be8 error 4 in libc-2.18.so[7f2eefebf000+1a0000]

And with gdb:
(gdb) run
Starting program: /usr/bin/mocp
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7ffff7ffa000
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5a090b6 in ?? () from /lib/x86_64-linux-gnu/libc.so.6

Didn't try to compile it because I think this is the last stable version but if it's necessary I'll probe.

I hope this would be valuable info to fix it. Thanks for your time and for this awesome player :-)

riesebie

Tue, 2014-03-11 08:47

This seems to be related to Debian Bug #740612

You can either downgrade to librcc0_0.2.9-3 or wait for librcc0_0.2.12-0.1 which will be uploaded the next few days.

Elimar

canselleiro

Fri, 2014-03-14 20:48

Oh, I saw issues about that library in this forum but I think that my case was not related.

Then I'll wait for the update :-)

Thanks for reply.

riesebie

Tue, 2014-03-18 08:16

librcc 0.2.12 is avaialble in sid now.

--
Elimar

canselleiro

Tue, 2014-03-18 17:18

Great!
Looking at the past in the package page it shouldn't take more than a month to be migrated to testing.
I'll use Quod Libet in between, another great player.

Thanks for the info :-)

riesebie

Mon, 2014-03-24 13:11

librcc0 0.2.12 is available in testing since 20th.

Elimar

canselleiro

Sat, 2014-04-05 15:11

Yes, and I can confirm that the segfault is gone.