[Bug 659139] gstpad: make some debug traces more useful

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Fri Sep 16 04:11:53 PDT 2011


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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |t.i.m at zen.co.uk
         Resolution|                            |FIXED
   Target Milestone|HEAD                        |0.10.36
           Severity|normal                      |trivial

--- Comment #5 from Tim-Philipp Müller <t.i.m at zen.co.uk> 2011-09-16 11:11:49 UTC ---
> You can have buffers with NULL caps (without being a bug elsewhere) ?

Yes, that just means "same as previous buffer". The first buffer must have caps
though (and really, all buffers *should* have caps, still..).

There's also the case of e.g. filesrc or souphttpsrc or so which don't put caps
on buffers and leave downstream to typefind them.


I've changed it so that it just doesn't mention the type if the buffer has NULL
caps, I don't think putting "[NULL caps]" in the log will add much information
(but more noise, IMHO).


 commit 91c217c714ceb052cecdbab61f48a1e3fb9955f7
 Author: Vincent Penquerc'h <vincent.penquerch at collabora.co.uk>
 Date:   Thu Sep 15 13:20:15 2011 +0100

    pad: make some debug traces more useful

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


PS: when you attach an updated patch, please make sure to check the right boxes
for 'Obsoletes: [ ] previous patch'

-- 
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