Hi Marcus, Yes that is what I'm thinking.
Larger question is why libusb in a UWP process or any process on Windows 10 IoT Core edition is unable to access devices. -----Original Message----- From: Marcus Meissner <mar...@jet.franken.de> Sent: April 27, 2019 6:34 AM To: Marek Sliwa <mareksl...@live.com> Cc: gphoto-devel@lists.sourceforge.net Subject: Re: [gphoto-devel] gphoto2/libgphoto2 on Windows IoT Core (or Desktop UWP app) Error : 'Out of memory' (-3) On Sat, Apr 27, 2019 at 03:43:36AM +0000, Marek Sliwa wrote: > Running gphoto2 mingw 64 bit binaries on Windows IoT Core and it is unable to > detect or load the usb library. Reproduce using : gphoto2.exe --debug > --debug-logfile=my-logfile.txt --auto-detect --summary > > The same binaries on desktop Windows 10 work just fine. However on Windows 10 > desktop this exact same error occurs when using libgphoto2 library directly > from a UWP app. Faults at the same point with same output trying to load the > usb1 iolib. > > Seems like it is unable to access or enumerate usb devices and the error > itself is misleading? > > This occurs with or without winusb driver installed for the Nikon camera and > weather it is connected or not. Seems like a general failure. Any ideas? > > Libusb is the cause or the error: > gp_port_library_list > libusb1.c:216<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmsys2%2FMINGW-packages%2Fissues%2F0&data=02%7C01%7C%7C44d1cc525fa64f6c5d2f08d6cb1540b9%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636919689467077350&sdata=0ea%2F1ztkA2K5T8qNl39wJRP8vqlIk2sMZIV4XLWcMyI%3D&reserved=0>: > Out of memory: 'descs = calloc (nrofdevs, sizeof(descs[0]))' failed. I guess nrofdevs is 0, and we erronously consider the NULL return as a bug. So the libusb you use here sees no USB devices, and this needs to be fixed. Ciao, Marcus _______________________________________________ Gphoto-devel mailing list Gphoto-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gphoto-devel
