[Bug 758584] gstbin: deadlock on state change?

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=758584

--- Comment #3 from mariuszb <mariusz.buras at gmail.com> ---
I'm not really sure what would I need to do to log element and peer_element as
all what I know is that they're both the same thing. It's a valid point that
this could be gdb optimising out some code and presenting confusing results.
I'll try to explore that further.

I've tried to hack the thing by adding a check in line 2005 against
peer_element != element and deadlock goes away but I'm not sure what other side
effects this would have. To me this proves that in that case element and
peer_element were the same. I have no clue how I could arrive at this
situation. The problem also goes away if I increase the debug level for gstbin
to 4.

I'll try to dig a bit more into that.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.