[Bug 727701] debugutils: Handle caps field values being NULL

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Sun Apr 6 06:26:47 PDT 2014


https://bugzilla.gnome.org/show_bug.cgi?id=727701
  GStreamer | gstreamer (core) | git

Tim-Philipp Müller <t.i.m> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |t.i.m at zen.co.uk
         Resolution|                            |FIXED
   Target Milestone|HEAD                        |1.3.1

--- Comment #2 from Tim-Philipp Müller <t.i.m at zen.co.uk> 2014-04-06 13:26:42 UTC ---
I would say that NULL string fields in caps are not valid, but I agree that the
code should still handle it. The real question is: where did you come across
this, which element created caps with a NULL string?!

commit e1e5183181f17a4dd342a3b64210b109131f2ed6
Author: Sebastian Rasmussen <sebras at hotmail.com>
Date:   Sun Apr 6 11:23:34 2014 +0200

    debugutils: Handle caps field values being NULL

    GST_DEBUG_BIN_TO_DOT_FILE() would cause a segfault whenever it encountered
an
    element's caps that had a field value being NULL. Such fields are
successfully
    handled e.g. by GST_*_OBJECT(), and with this patch so does
    GST_DEBUG_BIN_TO_DOT_FILE(). Even if string fields with a NULL value are
    not supposed to be valid in caps, such caps can be created.

    Fixes https://bugzilla.gnome.org/show_bug.cgi?id=727701

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


More information about the gstreamer-bugs mailing list