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 499168 - gst-launch does not abort always with gst-fatal-warnings
gst-launch does not abort always with gst-fatal-warnings
Status: RESOLVED WONTFIX
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-23 12:49 UTC by Thijs Vermeir
Modified: 2008-01-07 10:12 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Thijs Vermeir 2007-11-23 12:49:18 UTC
In this simple gst-launch pipeline there is a warning but gstreamer fails to abort:

:> gst-launch --gst-fatal-warnings filesrc location=1.mpg ! decodebin2 ! fakesink silent=true --gst-debug-level=2
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
0:00:00.335564000 31309 0x813f068 WARN            decodebin2 gstdecodebin2.c:1938:gst_decode_group_expose: Group 0x811fd68 still has 1 dynamic objects, not exposing yet
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
Got EOS from element "pipeline0".
Execution ended after 1325894000 ns.
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
FREEING pipeline ...
Comment 1 Wim Taymans 2007-11-27 18:21:00 UTC
The abort only happens for g_warning, not for the warnings in the debug system. Is this a problem or contrary to what you expected?
Comment 2 Thijs Vermeir 2007-11-28 09:43:52 UTC
Ah, OK. 
I expected that it also worked with the gst warnings.

Maybe we can make that as an feature?
Comment 3 Tim-Philipp Müller 2007-12-11 14:11:51 UTC
> I expected that it also worked with the gst warnings. 
> Maybe we can make that as an feature?

Is this really useful? (I mean, if you spot a problem in the debug log, you've got file and line number already in the output, so it's easy to set a break point in gdb and check what's happening. I think more often than not WARN messages aren't really things that need investigating).

Comment 4 Tim-Philipp Müller 2008-01-07 10:12:05 UTC
WONTFIX-ing for now, since I don't see how this would be useful in general (we don't use GST_WARNING that way). Feel free to re-open if you feel differently.