fusb_linux::_reap fails to distinguish between a non-recoverable error and "I didn't reap anything"
|Assignee:||Eric Blossom||% Done:||
From: Eric Blossom <[email protected]> To: Tom Rondeau <[email protected]> Cc: Bcc: Subject: Re: usb disconnect issue Reply-To: In-Reply-To: <[email protected]> On Thu, Sep 04, 2008 at 06:11:22PM -0400, Tom Rondeau wrote: > Eric, > > In usrp_basic.cc, usrp_basic_rx::stop(), there's a problem when the USRP > has been disconnected (power off or USB cable gets unplugged) where the > d_ephandle->stop() function never returns and keeps spitting "fusb::_reap" > to the console. You can't ^C out of it, either. > > To fix it, after the set_rx_enable(false) is called, it returns an error > and sets ok to false. I just use this to assume the system's lost contact > with the USRP, so I test it and don't called the d_ephandle->stop() > function if ok==false. > > This works, but I'm not sure it's the best way to go. Do you have any > thoughts, or is there maybe a better function to test? > > Thanks, > Tom I think it ought to be fixed in fusb_linux. It's failing to distinguish between a non-recoverable error and "I didn't reap anything". I'll come up with a patch. Eric