Request suggestions for debugging failed state change on nested bins.

Stirling Westrup swestrup at gmail.com
Fri Jan 4 09:18:59 PST 2013


I have a fairly complex setup for my application, and it can involve
elements nested inside bins inside other bins inside my pipeline.

Sometime when I make a small change, one of the elements fails to make
a state change, and my entire pipeline times out on the change.

In these cases I'd love some way to iterate through the pipeline's
elements and list which ones have not changed state. In the case of
bins that haven't changed, I'd like to iterate through them
recursively so that I can get a list of which lowermost elements
failed to transition. I think this would help me pin down errors more
quickly.

The thing is, I'm not sure how to go about doing this. If a pipeline
times out while changing state, are the states of the component
elements up to date, or not? Bins seem to keep an internal list of
which elements have yet to finish an async state change, but that is
private info that I am loathe to try to access, even in a debug
routine.

Any and all suggestions about how to go about this are welcome.

--
Stirling Westrup
Programmer, Entrepreneur.
https://www.linkedin.com/e/fpf/77228
http://www.linkedin.com/in/swestrup
http://technaut.livejournal.com
http://sourceforge.net/users/stirlingwestrup


More information about the gstreamer-devel mailing list