[gstreamer-bugs] [Bug 412678] random segfaults or memory corruptions which seem to be linked to textoverlay

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=412678

  GStreamer | don't know | Ver: 0.10.x


Tim-Philipp Müller changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEEDINFO




------- Comment #3 from Tim-Philipp Müller  2007-03-01 00:00 UTC -------

 - what versions of GStreamer core, -base and -good?

      $ gst-inspect-0.10 filesrc | grep Version
      $ gst-inspect-0.10 textoverlay | grep Version
      $ gst-inspect-0.10 videobox | grep Version

 - what version of v4l2src?

 - what distro?

 - could you make sure you've got full debugging symbols for
   GStreamer, gst-plugins-* and GLib, by installing the appropriate
   debug packages please?

 - can you reproduce the problem by using videotestsrc (maybe followed
   by a capsfilter forcing the same dimensions as your v4l2src give you)
   in place of the v4l2src?

 - can you reproduce the problem if you're running your pipeline in
   gst-launch-0.10? If yes, could you run it through valgrind please?

     $ G_SLICE=always-malloc valgrind --trace-children=yes gst-launch-0.10
...yourpipelinehere...  2>valgrind.log

   (this will only really be useful if you have full debug symbols).


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email