Captue "critical" messages

[Wes Miller]

Occasionally as I develop a new pipeline I will make an error that causes the
pipeline to emit critical warnings and/or critical errors.  These messages
just pop-up on my screen and, since I already have a bunch of program debug
print statements sending stuff to the screen, I don't always see them and
they aren't captured into my logs (program logs, not gst ones).

So, how do I capture these messages?  I assume there is a callback routine
to capture them.

Or, how do I programatically turn on gsgtreamer logging.  I'd prefer not to
use command line switches nor environment variables as this particular
project is a dll/so where I'd like to be able to let the main program
control the gst logging by a library call.  Of course, I'd also like to be
able to restrict the class/type of the logged information.

Thanks,

Wes




--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/Captue-critical-messages-tp4658794.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.