Alright, that explains what is happening. The device is getting disconnected
which triggers a call to usbi_handle_disconnect which cancels
usbi_handle_transfer_completion. You are then getting notification from the os
indicating the transfer failed. The fix I sent you avoid the segmentation fault
but will give you duplicate callbacks. Other paths may still get a segmentation
fault. I will work on a better fix over the weekend and get it in for 1.0.17.
-Nathan
On Jul 20, 2013, at 6:34 AM, Lilk <notificati...@github.com> wrote:
> Issue at least seems to be resolved by inserting the following at line 1534:
> if (itransfer->list.next)
>
> —
> Reply to this email directly or view it on GitHub.
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk_______________________________________________
> libusbx-devel mailing list
> libusbx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/libusbx-devel
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
