> Without getting to deep into this, the problem is in the shared > responsibilities between the Python world and the C++ world. I don't > completely understand the series of events, but the crux o the problem seems > to be who gets to the destructors first. >
its never easy is it... > In the case of your program, it's the self._qtgui_sink_x_0_win object that's > the problem. If you don't make it a member of the class, that is, drop the > "self." part, it _should_ work fine. My understanding, which could be wrong, > is that as a local variable, it gets destroyed in the right order. > I removed the "self." and still seeing the same results. But, you gave me an idea that there might be this unhappy deconstructor race condition. So, I tried deleting the qapp after exec() and that made it better. Also and rather, stopping the top block make it better; so maybe it was getting data to draw and somebody already destroyed the qt graphics stuff. So, the reason I didnt stop the top block: http://gnuradio.squarespace.com/examples I will give this a more conclusive test tomorrow, but the fix seems worth while anyhow. http://gnuradio.org/cgit/gnuradio.git/commit/?id=e762abc703e3224b54466685bf51b3fa90ee8edc -Josh _______________________________________________ Discuss-gnuradio mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
