Thanks!
It works now perfectly.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/160#issuecomment-29510111--
Rapidly troubleshoot problems before they affect your business.
Closed #160 via 68bd52920ce6043678f6d19d1f221930e7a214d5.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/160--
Rapidly troubleshoot problems before they affect your busines
> in windows_transfer_callback, just easy if (io_size > 0) after case
> ERROR_OPERATION_ABORTED: will help.
I don't think we want to fix this in `windows_transfer_callback()`, as we may
get `io_size` 0 when there is no error.
A more proper fix is to have `hid_copy_transfer_data()` accept an `io_
> Is libusbx still being maintained, or is all the energy focused on the great
> rejoining?
Don't know about the others, but for the past few weeks my energy has been
focused entirely on the [Rufus v1.4.0 release](http://rufus.akeo.ie) (which is
now in beta at long last - pfew!). I also had to
Right to say, the bug is in windows_transfer_callback, just easy if (io_size >
0) will help.
case ERROR_OPERATION_ABORTED:
- istatus = priv->apib->copy_transfer_data(SUB_API_NOTSET, itransfer,
io_size);
- if (istatus != LIBUSB_TRANSFER_COMPLETED) {
- usbi_dbg("Failed to copy par
Kerdo Link wrote:
>
> I have set a timeout 500ms in libusb_interrupt_transfer().
> ...
> libusbx: debug [windows_transfer_callback] handling I/O completion
> with errcode 995, size 0
>
I was wrong, you are right. CancelIo does, indeed, result in
ERROR_OPERATION_ABORTED. This does look like a bug
I have set a timeout 500ms in libusb_interrupt_transfer().
>From the debug log:
libusbx: debug [hid_submit_bulk_transfer] matched endpoint 81 with interface 0
libusbx: debug [hid_submit_bulk_transfer] reading 26 bytes (report ID: 0x00)
libusbx: debug [usbi_add_pollfd] add fd 2 events 1
libusbx: de
Kerdo Link wrote:
>
> I have a problem with libusb_interrupt_transfer under cygwin. When I
> want to read data from a USB device and there is nothing to receive, I
> get a Segmentation fault. I managed to backtrace the fault to
> hid_copy_transfer_data() in windows_usb.c, line:
> memcpy(transfer_pr
I have a problem with libusb_interrupt_transfer under cygwin. When I want to
read data from a USB device and there is nothing to receive, I get a
Segmentation fault. I managed to backtrace the fault to
hid_copy_transfer_data() in windows_usb.c, line:
memcpy(transfer_priv->hid_dest, transfer_pri
