GNOME Bugzilla – Bug 343057
gst-launch-0.10 segfaults when passed gst-plugin-path and bogus gst-debug flags
Last modified: 2006-08-21 07:59:31 UTC
Hi, This segfaults here: /usr/bin/gst-launch-0.10 --gst-debug=1 --gst-plugin-path=/usr/lib/gstreamer-0.10 (not that it's a --gst-debug, instead of --gst-debug-level) (gdb) run --gst-debug=1 --gst-plugin-path=/usr/lib/gstreamer-0.10 --gst-disable -segtrap Starting program: /usr/bin/gst-launch-0.10 --gst-debug=1 --gst-plugin-path=/usr/ lib/gstreamer-0.10 --gst-disable-segtrap (gdb) bt
+ Trace 68474
Bye,
Created attachment 66304 [details] [review] minimally invasive patch Crashes parsing caps. Not that surprising, since all the GStreamer types etc. are registered only in post_init. Maybe we should just move them to pre_init - not sure. Attached patch is minimally invasive.
2006-05-29 Tim-Philipp Müller <tim at centricular dot net> * gst/gst.c: (add_path_func), (init_post): Don't scan registry paths passed via --gst-plugin--path immediately (will crash, because absolutely nothing is set up and no types are registered etc.); do this later in init_post(). Fixes #343057.
*** Bug 347559 has been marked as a duplicate of this bug. ***