GNOME Bugzilla – Bug 740191
dvbbasesink: segfaults on 32-bit (rpi)
Last modified: 2015-09-13 12:34:36 UTC
I get this stack trace when running gmediarender[1] on a Raspberry Pi (ARM), but not when running it on a x86 (64bit) platform. I don't know whether the processor is the issue, it could also just be the different system. Both systems run Debian jessie (the Raspberry Pi runs the specialized ARM port Raspbian[2]). As removing gst-plugins-bad works around the problem, I believe one of the -bad plugins somehow causes the problem. Looking at the stack trace, it appears to be the dvb (?) plugin. I reported the issue in Raspbian as well [3], but realized it probably doesn't have anything to do with gmediarender or the Raspbian distro. Here's the full stack trace: Program received signal SIGSEGV, Segmentation fault. strchr () at ../ports/sysdeps/arm/armv6/strchr.S:28 28 ../ports/sysdeps/arm/armv6/strchr.S: No such file or directory. (gdb) bt
+ Trace 234333
[1] https://github.com/hzeller/gmrender-resurrect [2] http://raspbian.org/ [3] https://bugs.launchpad.net/raspbian/+bug/1392850
I think this should fix it: commit 3e1d7630187dd96b137553aec2c6edb60c213682 Author: Tim-Philipp Müller <tim@centricular.com> Date: Sat Nov 15 21:59:48 2014 +0000 dvbbasebin: fix possible crash by passing 64 bits for 64-bit queue property https://bugzilla.gnome.org/show_bug.cgi?id=740191 Would be great if you could try it and re-open if not, thanks!
Yes, that fixed it. Thank you for the quick reply! I tested this by applying the patch (manually) to the Debian source package 1.4.3-2 and building it. That fixed the issue. Then I removed the patch, to be sure, and indeed it segfaulted again. Building took 5½ hour (twice!) on this little 700MHz ARM board, so that's why it took so long to test.
Perfect, thanks for going through the trouble of verifying and confirming that's what it was!
(In reply to Ayke van Laethem from comment #2) > Yes, that fixed it. Thank you for the quick reply! > > I tested this by applying the patch (manually) to the Debian source package > 1.4.3-2 and building it. That fixed the issue. Then I removed the patch, to > be sure, and indeed it segfaulted again. > > Building took 5½ hour (twice!) on this little 700MHz ARM board, so that's > why it took so long to test. I know it have been a long time, but I have no choice. How can you did that? I have the same problem with Raspberry Pi.