Hi, Eric and Johnathan Thank you guys for the quick answer. I have done some tests with my code and got the following observation: I used a low-pass filter in the processing chain, if the decimation rate is set to 1, then fg.run() can return; if the decimation rate is set to any other integers, fg.run() won't. I am not sure whether this is something random in my machine or caused by the code itself.
BTW: Eric, you mentioned the gr_udp_source, I am quite interested in it, is there any example in the svn using this block? If so, please point some of them to me. Thanks. Dawei On 8/10/07, Johnathan Corgan <[EMAIL PROTECTED]> wrote: > > Dawei Shen wrote: > > > I used gr.head() as my source, so I assumed fg.run() should be able to > > return, but it doesn't. Anybody has any idea which could be the reason? > > Here is the error message if I press ctrl+C to stop the program. > > > > > > mygraph.run() > > File > > "/usr/local/lib/python2.5/site-packages/gnuradio/gr/flow_graph.py", line > > 113, in run > > self.wait () > > File > > "/usr/local/lib/python2.5/site-packages/gnuradio/gr/flow_graph.py", line > > 104, in wait > > self.scheduler.wait () > > File > > "/usr/local/lib/python2.5/site-packages/gnuradio/gr/scheduler.py", line > > 68, in wait > > thread.join(timeout) > > File "/usr/lib/python2.5/threading.py", line 569, in join > > self.__block.wait(delay) > > File "/usr/lib/python2.5/threading.py", line 233, in wait > > _sleep(delay) > > KeyboardInterrupt > > This may be a Python threading bug in 2.5. Eric, can you elaborate on > what you referring to in the other thread about our having to work > around in 2.3 and 2.4? > > In release 3.1 we won't be using Python threads anymore, so maybe it's a > moot point. > > -- > Johnathan Corgan > Corgan Enterprises LLC > http://corganenterprises.com >
_______________________________________________ Discuss-gnuradio mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
