Re: [Libusb-win32-devel] struct usb_device* lifetimes

[Dan E. <Dan...@ne...>]

Graeme Gill wrote:
> Dan Ellis wrote:
>=20
>> I've just spotted a problem which probably explains quite a bit of
>> strange behaviour which has been seen:
>>=20
>> When a device is unplugged, a subsequent call to usb_find_devices
>> will free the struct usb_device, even though some other part of the
>> software may have a handle open on the device, with the handle
>> structure holding a pointer of the (now invalid) device.
>=20
> This might explain why merely listing available USB devices corrupts
> and breaks an existing Libusb-win32 USB connection running in another
> process... =20

Maybe, but I thought that each process connected to a a DLL created a
new set of static variables? Certainly it can be a problem if more than
one thread lists available devices, or one thread lists the devices
while another one (or ones) use it.

Dan.