Re: [Discuss-gnuradio] Unrecognized exception in gr-uhd

[Josh Blum]

Looks like i removed an interruption disable in the libusb
implementation (that actually gets called externally by send/recv). Its
restored in the master now.

Do you mind pulling and retrying?
Thanks, -josh

On 01/21/2011 03:49 PM, Alexandru Csete wrote:
> Yes, I use USRP1 with WBX and RFX2400 and it occurs with both daughterboards
> Alex
> 
> On Sat, Jan 22, 2011 at 12:45 AM, Josh Blum <address@hidden> wrote:
>> probably a boost thread interrupt, help me narrow this down, are you
>> using USRP1? -Josh
>>
>> On 01/21/2011 03:38 PM, Alexandru Csete wrote:
>>> Greetings,
>>>
>>> Using the latest gnuradio/next v3.3.1git-865-gd429522b and UHD from
>>> yesterday (commit c14bbffbebb817fc1c622785094268fe68164c60) I get
>>> thread[thread-per-block[0]: <gr_block uhd single_usrp source (1)>]:
>>> caught unrecognized exception
>>> whenever I call the gr.top_block.unlock(), stop() and maybe also
>>> wait() functions.
>>>
>>> I have attached a simple Python script which triggers this exception.
>>> I am using USRP1 and the exception occurs with both WBX and RFX2400
>>> daughterboards
>>>
>>> I didn't notice any side effects. The receiver code where I discovered
>>> this performs some reconfiguration of the flow graph between lock()
>>> and unlock() and it continues to function after the exception.
>>>
>>> My previous reference is v3.3.1git-832-ga2262b6b from Jan 11 and UHD
>>> b4d58f3501596fdddf240d576d0b1b2cb5862892 where this issue did not
>>> occur.
>>>
>>> Alex
>>>
>>>
>>>
>>> _______________________________________________
>>> Discuss-gnuradio mailing list
>>> address@hidden
>>> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>> _______________________________________________
>> Discuss-gnuradio mailing list
>> address@hidden
>> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
> 
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio