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 741001 - GST_DEBUG categories are missing when using --gst-debug-help
GST_DEBUG categories are missing when using --gst-debug-help
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other All
: Normal minor
: 1.8.2
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-12-01 22:32 UTC by Linus Svensson
Modified: 2016-05-13 08:29 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
debug: Instantiate GType when dumping debug categories. (2.21 KB, patch)
2016-04-01 14:09 UTC, Jan Schmidt 		none Details | Review

Description Linus Svensson 2014-12-01 22:32:18 UTC 
GST_DEBUG defined in class_init is not listed when using --gst-debug-help.

Only categories defined as part of G_DEFINE_TYPE_WITH_CODE are seen in the list.
Comment 1 Jan Schmidt 2016-04-01 03:24:05 UTC 
I guess that makes sense. To fix it, we'd either need to make a rule about when debug categories should be registered (and fix it everywhere), or else make that mode of gst-inspect create an instance of each type so that the class_init function is called.

The second option seems easier, and is what gst-inspect -a does anyway.
Comment 2 Jan Schmidt 2016-04-01 14:09:25 UTC 
Created attachment 325159 [details] [review]
debug: Instantiate GType when dumping debug categories.

A lot of debug categories are declared in element class_init
functions, which don't get run until the element is first created
(not just registered in the plugin load function). This means
that --gst-debug-help doesn't print out a lot of categories.

Creating an instance of each element from the element factory
makes them visible, at some extra cost - 2-3 times longer, which can
be a full second or two of extra waiting. Yikes!
Comment 3 Jan Schmidt 2016-05-13 08:29:53 UTC 
Apparently I didn't actually push this - updating to 1.8.2