GNOME Bugzilla – Bug 378130
mpc decoder crash with libmpcdec3 package from rarewares.org
Last modified: 2007-01-08 22:34:33 UTC
What were you doing when the application crashed? add .mpc file to exaile / rhythmbox gstreamer problem sorry my english Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 93118464 vsize: 0 resident: 93118464 share: 0 rss: 26763264 rss_rlim: 0 CPU usage: start_time: 1164202377 rtime: 0 utime: 397 stime: 0 cutime:358 cstime: 0 timeout: 39 it_real_value: 0 frequency: 6 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1227180368 (LWP 4448)] [New Thread -1294173280 (LWP 5419)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 88507
Thread 2 (Thread -1294173280 (LWP 5419))
Thanks for the bug report. A few questions: 1) Can you reproduce the bug? 2) Does this work? $ gst-launch-0.10 playbin uri=file:///path/to/file.mpc 3) Do you still have the .mpc file that causes this issue? Can you make it available somewhere?
*** Bug 386625 has been marked as a duplicate of this bug. ***
Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 133607424 vsize: 0 resident: 133607424 share: 0 rss: 25243648 rss_rlim: 0 CPU usage: start_time: 1166383068 rtime: 0 utime: 132 stime: 0 cutime:124 cstime: 0 timeout: 8 it_real_value: 0 frequency: 11 Backtrace was generated from '/usr/bin/totem' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225345360 (LWP 6735)] [New Thread -1328198752 (LWP 6757)] [New Thread -1311413344 (LWP 6755)] [New Thread -1303020640 (LWP 6754)] [New Thread -1294627936 (LWP 6753)] [New Thread -1286235232 (LWP 6752)] [New Thread -1270514784 (LWP 6743)] [New Thread -1261212768 (LWP 6742)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 94927
Thread 3 (Thread -1311413344 (LWP 6755))
Thanks for the detailed stack trace! Not sure what's going on here though I'm afraid. If you could make the .mpc file available somewhere (or send it by e-mail) that would be really useful [*]. Does this crash as well? $ gst-launch-0.10 playbin uri=file:///path/to/foo.mpc If yes, could you also do one or both of these things: 1) create a full debug log with: $ export GST_DEBUG_NO_COLOR=1 $ GST_DEBUG=*:5 gst-launch-0.10 playbin uri=file:///path/to/foo.mpc 2>dbg.log $ bzip2 dbg.log and then attach the dbg.log.bz2 file to this bug report. 2) run things in valgrind (after' sudo apt-get install valgrind') $ valgrind gst-launch-0.10 playbin uri=file:///path/to/foo.mpc 2> valgrind.log and then attach the valgrind.log file to this bug report. [*] if it crashes at the beginning, maybe part of the file can reproduce the problem too: $ head --bytes=900k file.mpc > file-beginning.mpc $ gst-launch-0.10 playbin uri=file:///path/to/file-beginning.mpc if the above crashes too, please attach file-beginning.mpc to this bug report or send it to me by e-mail if possible.
Created attachment 78552 [details] GStreamer log with GST_DEBUG_5 on Thanks for the answer, tpm! Your (and all of GStreamer developer's) work is greatly appreciated. As for the questions: 1) Yes, gst-launch-0.10 crashes too. Even the first 900k. I will email you the file. 2) No problem! I just attached those logs. I spent a few hours trying to look at your code, and I can't see what's wrong, too. Please attach the patch in this bug once you discover that. I'm curious ;)
Created attachment 78553 [details] Valgrind log
I am stupid, stupid, stupid! Rarewares, which I added to my sources.list for a totally different reason, had updated my libmpcdec3. After I downgraded things, they worked fine. Here is the line that caused the trouble, just in case someone else reports the same thing: #deb http://www.rarewares.org/debian/packages/unstable/ ./ Thanks for your time, and sorry for the confusion.
Ah, thanks. So it's an ABI issue of some sort then. Could you tell me what the libmpcdec3 version number was that caused the breakage?