[gstreamer-bugs] [Bug 573369] [gstfaad] Memory corruption and segfault

GStreamer (bugzilla.gnome.org) bugzilla-daemon at bugzilla.gnome.org
Sun Mar 1 08:16:50 PST 2009


If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=573369

  GStreamer | gst-plugins-bad | Ver: git

Edward Hervey changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|major                       |blocker
            Summary|[gstfaad] Crashes using     |[gstfaad] Memory corruption
                   |faad2-2.7 (memory corruption|and segfault
                   |?)                          |
   Target Milestone|HEAD                        |0.10.11




------- Comment #4 from Edward Hervey  2009-03-01 16:17 UTC -------
and it gets worse...

This was all due to our 'redefinition' of the init prototypes at the top of
gstfaad.c

extern long faacDecInit (faacDecHandle, guint8 *, guint32, guint32 *, guint8
*);
extern int8_t faacDecInit2 (faacDecHandle, guint8 *, guint32,
    guint32 *, guint8 *);


We force the samplerate argument to be a (guint32 *), whereas they've now fixed
their issues, and the public headers are now in sync with the internal ones.

What do we do ? pushing this up to blocker.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=573369.




More information about the Gstreamer-bugs mailing list