GNOME Bugzilla – Bug 499168
gst-launch does not abort always with gst-fatal-warnings
Last modified: 2008-01-07 10:12:05 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 ...
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?
Ah, OK. I expected that it also worked with the gst warnings. Maybe we can make that as an feature?
> 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).
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.