Re: [pyusb-users] pyusb get_active_configuration segfault

2011-09-27 Thread Wander Lairson Costa
2011/9/26 Tormod Volden : > On Mon, Sep 19, 2011 at 1:18 PM, Wander Lairson Costa wrote: >> 2011/9/17 Peter Bigot: >>> The following program causes a segfault using libusb-1.0: >>> >>>  import usb >>>  rf2500 = usb.core.find(idVendor=0x0451, idProduct=0xF432) >>>  cfg = rf2500.get_active_configurat

Re: [pyusb-users] pyusb get_active_configuration segfault

2011-09-26 Thread Tormod Volden
On Mon, Sep 19, 2011 at 1:18 PM, Wander Lairson Costa wrote: > 2011/9/17 Peter Bigot: >> The following program causes a segfault using libusb-1.0: >> >>  import usb >>  rf2500 = usb.core.find(idVendor=0x0451, idProduct=0xF432) >>  cfg = rf2500.get_active_configuration() >> >> due to libusb_get_conf

Re: [pyusb-users] pyusb get_active_configuration segfault

2011-09-19 Thread Wander Lairson Costa
2011/9/17 Peter Bigot : > The following program causes a segfault using libusb-1.0: > >  import usb >  rf2500 = usb.core.find(idVendor=0x0451, idProduct=0xF432) >  cfg = rf2500.get_active_configuration() > > due to libusb_get_configuration being invoked with a null device > handle.  The fix is as b

[pyusb-users] pyusb get_active_configuration segfault

2011-09-17 Thread Peter Bigot
The following program causes a segfault using libusb-1.0: import usb rf2500 = usb.core.find(idVendor=0x0451, idProduct=0xF432) cfg = rf2500.get_active_configuration() due to libusb_get_configuration being invoked with a null device handle. The fix is as below: diff --git a/usb/core.py b/usb/