Hi Lefteris, I still don't know why you *kill* the process. GNU Radio waits for *any* key, and pressing anything but ctrl-C should let the flow graph shut down correctly, in turn deallocating the UHD sources/sinks, which should free the libusb device handles.
Greetings, Marcus On 05.11.2014 22:53, Eleftherios(Lef) Kampianakis wrote: > Sylvain thank you for your reply, > > Ok, what about the python script in my previous message? How can I write my > code in order to prevent the LIB_USB_ERROR_PIPE message. No matter how I > stop the gnuradio script (e.g. catch keyboard interrupt and issue stop() > and wait as in my original post), I always get the same message. My > intuition due to that is that something is not cleaned up properly in UHD > level. Any suggestions on that? > > Best regards > Lefteris > > On Wed, Nov 5, 2014 at 12:52 PM, Sylvain Munaut <[email protected]> wrote: > >>> After this point the only thing that I can do is remove and re-insert the >>> USB from the computer in order for my script to work. I assume this is >> not >>> normal behavior (and also not a programming error) because this is a >> minimum >>> working example, and its not working. >> There is literally nothing GNURadio can do about this. >> >> When you press the 'red cross' button, it _kills_ the whole process >> (SIGKILL), a process cannot catch this signal, nor do anything about >> it (i.e. not a single instruction of gnuradio will execute after this) >> >> At this point, it's up to the operating system to clean up any state >> of the process ... >> >> >> Cheers, >> >> Sylvain >> > > > > > _______________________________________________ > Discuss-gnuradio mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
_______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
