FYI: liborc in testing is badly broken (stack corruption)

Arno Schuring aelschuring at hotmail.com
Sat Apr 30 12:05:58 UTC 2011


Hi,

since I haven't been able to find any references to this bug (not on
the BTS nor on the ML), I'll just put it out here to let you guys know.

liborc-0.4-0 version 1:0.4.13-1 causes any media player (I've tried)
that relies on gstreamer to fail with segfaults. The exact behaviour
differs between the programs though:

rhythmbox - crashes at first play (start of file)
quodlibet - crashes at song change (end of file)
totem - crashes when changing volume

The backtraces all look similar (compare with bt from totem thread 2)
quodlibet:
Core was generated by `python /usr/bin/quodlibet --start-playing'.
Program terminated with signal 11, Segmentation fault.
#0  0xb0158b4a in ?? ()
(gdb) bt
#0  0xb0158b4a in ?? ()
#1  0x00000900 in ?? ()
#2  0x00000000 in ?? ()

totem:
Core was generated by `totem /media/[..]'.
Program terminated with signal 11, Segmentation fault.
#0  0xafe5dc65 in ?? ()
(gdb) bt
#0  0xafe5dc65 in ?? ()
#1  0x00002000 in ?? ()
#2  0xb6bad03c in ?? () from /usr/lib/libgobject-2.0.so.0
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb) thread 2
[Switching to thread 2 (Thread 3966)]#0  0xb77a9424 in
__kernel_vsyscall () (gdb) bt
#0  0xb77a9424 in __kernel_vsyscall ()
#1  0xb740ff7f in __pthread_cond_wait (cond=0xa34ca28, mutex=0xa34d7c8)
    at pthread_cond_wait.c:153
#2  0xb239aa46 in gst_queue_chain (pad=0xa306190, buffer=0xa4fa2e0)
    at gstqueue.c:995
#3  0xb6c082c0 in gst_pad_push (pad=0xa2c79c0, buffer=0xa4fa2e0)
    at gstpad.c:4665
#4  0xb6bf186d in gst_proxy_pad_do_chain (pad=0xa30aa38,
buffer=0xa4fa2e0) at gstghostpad.c:163
[..]

rhythmbox:
Core was generated by `rhythmbox'.
Program terminated with signal 11, Segmentation fault.
#0  0xb0e9d5e5 in ?? ()
(gdb) bt
#0  0xb0e9d5e5 in ?? ()
#1  0x00000800 in ?? ()
#2  0xb6b1103c in ?? () from /usr/lib/libgobject-2.0.so.0
Backtrace stopped: previous frame inner to this frame (corrupt stack?)


I have already upgraded to 1:0.4.14-1 (from incoming) which fixes the
problem. However since it's not even in unstable, it will take more
than ten days to get this fix in testing.


Hope this helps anyone running into the same issue,
Arno



More information about the pkg-gstreamer-maintainers mailing list