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 138635 - two GLib-GObject-CRITICAL Messages when running gst-register-0.8 with a certain LADSPA plugin
two GLib-GObject-CRITICAL Messages when running gst-register-0.8 with a certa...
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins
git master
Other Linux
: Normal normal
: 0.8.1
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-03-31 13:40 UTC by Stefan Sauer (gstreamer, gtkdoc dev)
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4


Attachments
checks and corrects ladspa parameter bounds, before using them as g_param_specs (2.26 KB, patch)
2004-04-05 17:04 UTC, Stefan Sauer (gstreamer, gtkdoc dev)
none Details | Review

Description Stefan Sauer (gstreamer, gtkdoc dev) 2004-03-31 13:40:14 UTC
* install the LADSPA plugin from
http://www.tux.org/pub/tux/ladspa/alienwah-1.11.tar.gz
* rerun gst-register
...
(process:20495): GLib-GObject-CRITICAL **: file gparamspecs.c: line 1846
(g_param_spec_float): assertion `default_value >= minimum && default_value <=
maximum' failed
(process:20495): GLib-GObject-CRITICAL **: file gobject.c: line 275
(g_object_class_install_property): assertion `G_IS_PARAM_SPEC (pspec)' failed

* running with gdb and --gst-fatal-warnings the backtrace is
  • #0 kill
    from /lib/i686/libc.so.6
  • #1 pthread_kill
    from /lib/i686/libpthread.so.0
  • #2 raise
    from /lib/i686/libpthread.so.0
  • #3 raise
    from /lib/i686/libc.so.6
  • #4 abort
    from /lib/i686/libc.so.6
  • #5 g_logv
    from /opt/gnome/lib/libglib-2.0.so.0
  • #6 g_log
    from /opt/gnome/lib/libglib-2.0.so.0
  • #7 g_param_spec_float
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #8 gst_ladspa_class_init
    at gstladspa.c line 361
  • #9 type_class_init_Wm
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #10 g_type_class_ref
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #11 gst_element_register
    at gstelementfactory.c line 204
  • #12 ladspa_describe_plugin
    at gstladspa.c line 986
  • #13 LADSPADirectoryPluginSearch
    at search.c line 81
  • #14 LADSPAPluginSearch
    at search.c line 127
  • #15 plugin_init
    at gstladspa.c line 1008
  • #16 gst_plugin_register_func
    at gstplugin.c line 200
  • #17 gst_plugin_load_file
    at gstplugin.c line 365
  • #18 gst_xml_registry_rebuild
    at gstxmlregistry.c line 1367
  • #19 gst_registry_rebuild
    at gstregistry.c line 182
  • #20 main
    at gst-register.c line 121

Comment 1 Stefan Sauer (gstreamer, gtkdoc dev) 2004-04-01 12:48:44 UTC
gst-compprep-0.8 is triggering that too.
 
(process:21602): GLib-GObject-CRITICAL **: file gparamspecs.c: line 1846
(g_param_spec_float): assertion `default_value >= minimum && default_value <=
maximum' failed
 
(process:21602): GLib-GObject-CRITICAL **: file gobject.c: line 275
(g_object_class_install_property): assertion `G_IS_PARAM_SPEC (pspec)' failed
 
(process:21602): GLib-GObject-CRITICAL **: file gparamspecs.c: line 1846
(g_param_spec_float): assertion `default_value >= minimum && default_value <=
maximum' failed
 
** (process:21602): CRITICAL **: file dparammanager.c: line 618
(gst_dpman_new_wrapper): assertion `param_spec != NULL' failed
 
** (process:21602): CRITICAL **: file dparammanager.c: line 234
(gst_dpman_add_required_dparam_direct): assertion `dpwrap != NULL' failed
 
** (process:21602): WARNING **: 0 sink pads, 2 src pads not yet supported
Comment 2 Stefan Sauer (gstreamer, gtkdoc dev) 2004-04-05 17:04:20 UTC
Created attachment 26362 [details] [review]
checks and corrects ladspa parameter bounds, before using them as g_param_specs

when initialising a g_param_spec with wrong values, the user will get a glib
critical message, this prevents it from happening [in this case ;-)].
I notified the original ladspa plugin author to fix it as well.
Comment 3 Benjamin Otte (Company) 2004-04-05 17:32:55 UTC
applied.