[prev in list] [next in list] [prev in thread] [next in thread] 

List:       libusb-devel
Subject:    Re: [libusb] "Corrupted" device-list returned from libusb_get_device_list on msys2/win10 with libusb
From:       David Grayson <davidegrayson () gmail ! com>
Date:       2016-08-22 0:49:11
Message-ID: CAJ127Vwz7iBVYD1ASBeo1WhHFnW+6JnpwwLmFMd+u-PpkKtDFA () mail ! gmail ! com
[Download RAW message or body]

Hello, Oli.

There was a discussion of this problem on this list in February:

https://sourceforge.net/p/libusb/mailman/libusb-devel/thread/56BA2716.8030009%40suprocktech.com/#msg34836232


--David Grayson

On Sat, Aug 20, 2016 at 5:56 PM, Oliver Meier <h2obrain@gmail.com> wrote:
> Hello
> 
> I get this strange behaviour in windows 10 where a corrupted device list is
> returned the first time it is requested.
> When libusb_bug.c is compiled in msys2 with 'gcc `pkg-config libusb-1.0
> --cflags` -o libusb_bug.exe libusbbug_exe.c' it's output look as follow:
> $ ./libusb_bug.exe
> libusb-version : 1.0.20.11004
> 
> corrupted device list:
> cnt_corrupted: 18
> device[ 0] => device_address:  1, busid:  1, portid: 208
> device[ 1] => device_address:  1, busid:  2, portid: 208
> device[ 2] => device_address:  7, busid:  3, portid: 09.04
> device[ 3] => device_address:  2, busid:  1, portid: 01
> device[ 4] => device_address:  8, busid:  3, portid: 09.03.03
> device[ 5] => device_address:  2, busid:  3, portid: 04
> device[ 6] => device_address:  6, busid:  3, portid: 09.03
> device[ 7] => device_address:  4, busid:  3, portid: 09
> device[ 8] => device_address:  3, busid:  3, portid: 03
> device[ 9] => device_address:  7, busid:  3, portid: 09.04
> device[10] => device_address:  3, busid:  3, portid: 03
> device[11] => device_address:  1, busid:  3, portid: 03
> device[12] => device_address:  5, busid:  3, portid: 18
> device[13] => device_address: 29, busid:  3, portid: 02
> device[14] => device_address: 22, busid:  3, portid: 01
> device[15] => device_address: 29, busid:  3, portid: 02
> device[16] => device_address:  2, busid:  2, portid: 01
> device[17] => device_address: 22, busid:  3, portid: 01
> 
> correct device list:
> cnt: 14
> device[ 0] => device_address:  1, busid:  1, portid: 01
> device[ 1] => device_address:  1, busid:  2, portid: 01
> device[ 2] => device_address:  2, busid:  1, portid: 01
> device[ 3] => device_address:  8, busid:  3, portid: 09.03.03
> device[ 4] => device_address:  2, busid:  3, portid: 04
> device[ 5] => device_address:  6, busid:  3, portid: 09.03
> device[ 6] => device_address:  4, busid:  3, portid: 09
> device[ 7] => device_address:  3, busid:  3, portid: 03
> device[ 8] => device_address:  7, busid:  3, portid: 09.04
> device[ 9] => device_address:  1, busid:  3, portid: 09
> device[10] => device_address:  5, busid:  3, portid: 18
> device[11] => device_address: 29, busid:  3, portid: 02
> device[12] => device_address:  2, busid:  2, portid: 01
> device[13] => device_address: 22, busid:  3, portid: 01
> 
> 
> The corrupted device list contains some duplicated devices.
> What I know for sure is that I can't connect to device 13 in the corrupted
> list and that after connecting to device 11 on the correct list and doing
> some control transfers, the next device list is receive with
> libusb_get_device_list is corrupted again.
> 
> I have no idea where to start debugging this problem, so I thought it is the
> easiest way (for me ;)) to just post this issue to your mailing list.
> 
> Cheers,
> Oli
> 
> ------------------------------------------------------------------------------
> 
> _______________________________________________
> libusb-devel mailing list
> libusb-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/libusb-devel
> 

------------------------------------------------------------------------------
_______________________________________________
libusb-devel mailing list
libusb-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-devel


[prev in list] [next in list] [prev in thread] [next in thread]