Which version of libusb(x) are you using? This sounds like an issue that
was present in an older version (fixed by commit
858b794cf10ff1ac76a4f453bed7645aa9709c44).
Chris
On Thu, Feb 13, 2014 at 2:29 PM, Erik Rull wrote:
> Hi Chris,
>
> thanks for your interesting explanation.
>
> No, I haven'
Hi Chris,
thanks for your interesting explanation.
No, I haven't registered any callbacks. I'm using the connect to an
interface and doing bulk reads and bulk writes - no async handling. I would
expect to get a libusb return code that tells me "hey the device is no
longer there" on which I cou
This line tells a lot of the story:
[ 6.849000] [1fae] libusbx: debug [libusb_unref_device] destroy device
2.57
This can only happen when a device's refcount == 0, which should not happen
while an active transfer is occurring. When a device is enumerated, its
refcount is 1. When you open the
Hi all,
during the debug for the unplug issue reported, I encounter now SIGSEGVs on
other places:
I added some debug output to the libusb/io.c:
int usbi_handle_transfer_completion(struct usbi_transfer *itransfer,
enum libusb_transfer_status status)
{
struct libusb_transfer *trans
tks very much it works
-- Original --
From: "Chris Dickens";;
Date: Thu, Feb 13, 2014 06:18 AM
To: "libusbx-devel";
Subject: Re: [Libusbx-devel] why not support hotplug usb ?
The linker is linking against your system's libusb at runtime instead of your
c
