After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 638234 - gstreamer was affected by recent change in glibc memcpy
gstreamer was affected by recent change in glibc memcpy
Status: RESOLVED NOTGNOME
Product: GStreamer
Classification: Platform
Component: dont know
0.10.31
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-12-29 00:36 UTC by promac
Modified: 2010-12-29 10:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description promac 2010-12-29 00:36:11 UTC 
This is on Fedora 14, 64 bits.

There is a long thread about the consequences of changing
memcpy to copy backwards.

Please, see comments #162 and #163, which are related to gstreamer:

https://bugzilla.redhat.com/show_bug.cgi?id=638477

Thanks.
Comment 1 Edward Hervey 2010-12-29 09:32:38 UTC 
An LD_PRELOAD which checks the arguments to memcpy and raises an exception when 'dangerous' would help to locate the faulty call.

Tracking down the gazillion memcpy calls by hand is not really an option.

Can a F14 user do this ?
Comment 2 promac 2010-12-29 10:26:42 UTC 
Hi,

I tracked down the problem using valgrind,
and the culprit was a libgstflump3dec.so
in my ~/.gstreamer-0.10/plugins/

This plugin was dated from 2007. After deleting it,
gstreamer is working just fine.

However, this plugin has never caused any trouble before, though.

Thanks.
Comment 3 Sebastian Dröge (slomo) 2010-12-29 10:29:12 UTC 
Please report this bug at Fluendo then: https://core.fluendo.com/gstreamer/trac/