Re: [Libusbx-devel] [libusbx] break from never ending loop. fix #76. (#167)

2014-01-10 Thread Kustaa Nyholm
As complete outside to this thread observing from the far: I don't understand Hans approach here. I looks to me that here we have Miguel with a reproducible case where a an infinite loop inside libusb can be triggered by disturbing the USB communication externally without touching the code in an

Re: [Libusbx-devel] [libusbx] break from never ending loop. fix #76. (#167)

2014-01-10 Thread miguelfreitas
I already explained what causes the EFAULT, and it is not bad pointer, but you don't want to hear. so sorry. --- Reply to this email directly or view it on GitHub: https://github.com/libusbx/libusbx/pull/167#issuecomment-32019265

Re: [Libusbx-devel] [libusbx] Core: libusb_interrupt_transfer and libusb_control_transfer does not return in case of error (#76)

2014-01-10 Thread miguelfreitas
Are you seriously not conceding that EFAULT can be caused by trying to write more bytes than the size of the buffer, instead of a bad pointer? If so, you should read more kernel code, cause at least in ARM with MMU this is explicitly checked. You have also not provided any arguments of why the

Re: [Libusbx-devel] libusb_set_configuration() function hangs

2014-01-10 Thread Xiaofan Chen
On Fri, Jan 10, 2014 at 3:19 PM, Pradeepa Senanayake wrote: > So in that case, with this new release which I got through > http://libusb.info/ what are the compatible drivers? > > https://github.com/libusb/libusb/wiki/Windows -- Xiaofan

Re: [Libusbx-devel] [libusbx] break from never ending loop. fix #76. (#167)

2014-01-10 Thread Hans de Goede
Closed #167. --- Reply to this email directly or view it on GitHub: https://github.com/libusbx/libusbx/pull/167-- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLi

Re: [Libusbx-devel] [libusbx] break from never ending loop. fix #76. (#167)

2014-01-10 Thread Hans de Goede
as discussed to dead in issue #76 the problem you're seeing and trying to fix is caused by a bad pointer *somewhere* as the EFAULT clearly indicated. Strong NACK from me. For the last time stop trying to propagate the EFAULT, do your homework and debug the cause of the EFAULT and fix that, than

Re: [Libusbx-devel] [libusbx] Core: libusb_interrupt_transfer and libusb_control_transfer does not return in case of error (#76)

2014-01-10 Thread Hans de Goede
Closed #76. --- Reply to this email directly or view it on GitHub: https://github.com/libusbx/libusbx/issues/76-- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLi

Re: [Libusbx-devel] [libusbx] Core: libusb_interrupt_transfer and libusb_control_transfer does not return in case of error (#76)

2014-01-10 Thread Hans de Goede
An EFAULT error indicates we've have bad pointers and are writing / reading random memory at that point all bets are off. If you can show me a real-world example where we get another error then EFAULT and go into an infinite loop, then I'm interested in fixing that. For the EFAULT problem you ne