The last problem which I posted is solved and now finally I got the backtrace
of error, which is the following:
------------------------------------------------------------------------------------------------------
#0 0xb710c289 in std::_List_node_base::hook () from /usr/lib/libstdc++.so.6
#1 0xb54e324a in fusb_ephandle_linux::completed_list_add (this=0x4f766660,
urb=0x8d5ec88) at /usr/include/c++/4.2.1/bits/stl_list.h:1162
#2 0xb54e364b in fusb_devhandle_linux::_reap (this=0x8d50888,
ok_to_block_p=true) at fusb_linux.cc:268
#3 0xb54e37b2 in fusb_ephandle_linux::reload_read_buffer (this=0x8d508a0)
at fusb_linux.cc:609
#4 0xb54e38b0 in fusb_ephandle_linux::read (this=0x8d508a0,
buffer=0xb4a640ec, nbytes=14336) at fusb_linux.cc:575
#5 0xb54d69e9 in usrp_basic_rx::read (this=0x8d50600, buf=0xb4a640ec,
len=14336, overrun=0xb4a680fb) at usrp_basic.cc:607
#6 0xb54a2de7 in usrp1_source_base::work (this=0x8d42e58,
noutput_items=3584,
[EMAIL PROTECTED], [EMAIL PROTECTED])
at usrp1_source_base.cc:105
#7 0xb60a80fa in gr_sync_block::general_work (this=0x8d42e58,
noutput_items=3584, [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]) at gr_sync_block.cc:64
#8 0xb60a6194 in gr_single_threaded_scheduler::main_loop (this=0x8d74788)
at gr_single_threaded_scheduler.cc:338
#9 0xb60a76dd in gr_single_threaded_scheduler::run (this=0x8d74788)
at gr_single_threaded_scheduler.cc:86
#10 0xb60a51d4 in gr_scheduler_thread::run_undetached (this=0x8d74a20,
arg=0x0)
at gr_scheduler_thread.cc:98
---------------------------------------------------------------------------------------------------------------------
Can some help me to understand it and let me know where is the error.
Best Regards
Kaleem Ahmad
Eric Blossom wrote:
>
> On Sat, Oct 11, 2008 at 09:33:15AM -0700, kaleem ahmad wrote:
>>
>> Thanks Johnathan,
>>
>> I am tring following as you suggested:
>>
>> "The usrp.source_c block only has one output, so you just connect:
>>
>> fg.connect(src, fg1)
>> fg.connect(src, fg2)"
>
>
>> But by doing this my fg2 is working but fg1 is not...It seems as the
>> connection of fg1 is overwritten by fg2???
>
> This definitely works. We use it all the time.
>
>
>> By the way I am using gnuradio3.1.1...is there any update in connect
>> method
>> in later versions?
>> By the way I have also tried following:
>>
>> fg.connect(src, fg1)
>
> You need to be using gr.top_block code, not gr.flow_graph, then
> bracket the reconfigration with self.lock() and self.unlock().
>
> self.lock()
>
> disconnect_all()
> self.connect(src,fg2)
> .......
> disconnect_all()
> self.connect(src,fg1)
>
> self.unlock()
>
> See usrp_siggen.py for example usage.
>
> Eric
>
>
>
>> ........
>> while(1):
>> disconnect_all()
>> fg.connect(src,fg2)
>> .......
>> disconnect_all()
>> fg.connect(src,fg1)
>>
>> But it is also not working? any suggestion for both of these methods?
>> Best Regards
>> Kaleem Ahmad
>
>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
--
View this message in context:
http://www.nabble.com/Error-while-receiving-tp19900161p20030693.html
Sent from the GnuRadio mailing list archive at Nabble.com.
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
