gst_debug_log_valist: assertion `category != NULL' failed

[Paddy]

Hi All,

I'm getting this from a call to gst_debug_log: "gst_debug_log_valist: assertion `category != NULL' failed"

Does anybody know what this is & how to fix it (if it's truly a problem)

Cheers

paddy

[Tim-Philipp Müller-2]

On Tue, 2012-12-18 at 09:28 -0800, Paddy wrote:

Hi,

> I'm getting this from a call to gst_debug_log: "gst_debug_log_valist:
> assertion `category != NULL' failed"
>
> Does anybody know what this is & how to fix it (if it's truly a problem)

It usually indicates a bug in some plugin, which is trying to log some
debug messages to a debug category that hasn't been initialized yet.

You can run your app/code with

 G_DEBUG=fatal_warnings gdb --args ./yourapp

to see where the warning comes from (it will then abort instead of
printing the warning, and you can get a stack trace).

Cheers
 -Tim

_______________________________________________
gstreamer-devel mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Paddy]

Cheers Tim,

There was no bug - just a call to gst_debug_log() that was invoked before GST_DEBUG_CATEGORY_INIT(), just as you said it would be :)

Is GST_DEBUG_CATEGORY_INIT() safe to call multiple times - there's no mention either way in the docs.

Thanks,

Paddy

[Tim-Philipp Müller-2]

On Wed, 2012-12-19 at 03:57 -0800, Paddy wrote:

> There was no bug - just a call to gst_debug_log() that was invoked before
> GST_DEBUG_CATEGORY_INIT(), just as you said it would be :)
>
> Is GST_DEBUG_CATEGORY_INIT() safe to call multiple times - there's no
> mention either way in the docs.

Yes, it is (but not thread-safe). You should usually call it somewhere
where it's only called once, e.g. in a plugin's plugin_init() function,
or type function, or class_init function or so. In an app somewhere
around gst_init().

Cheers
 -Tim

_______________________________________________
gstreamer-devel mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel