Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

> On 2012.07.28 12:06, Ludovic Rousseau wrote: > You would get more detailed information by rebuilding libusbx with debug > info. As you suggested, I compiled libusbx with debug info. I'd like you to have a final look at the attached backtrace and confirm that the segmentation fault is related to

Re: [Libusbx-devel] [PATCH] Fix unconditional disarming of timerfd

On 2012.08.01 12:52, Hans de Goede wrote: > Hmm, I hadn't noticed the explicit disarm there, since the > handle_timeouts_locked code just cancels > transfers and does not do anything io-intensive, the run-time for > handle_timeouts_locked will be > short, so I see no value in the disarm there, and

Re: [Libusbx-devel] Compiling on a fresh installation on Mac OS X

On 2012.07.23 12:53, Pete Batard wrote: > I think README.git is probably better as well. Will try to add one soon. Pushed. Regards, /Pete -- Live Security Virtual Conference Exclusive live event will cover all the ways

Re: [Libusbx-devel] USB network hub -> get_device_list gives "could not retrieve port number for device"

Hi Casey, On 2012.07.31 04:12, Casey Bajema wrote: > I'm trying to use a USB device over a Belkin network hub > That's an interesting device... > * The problem seems to be that the network hub doesn't provide a valid > port number (in the device manag

Re: [Libusbx-devel] [PATCH] Fix unconditional disarming of timerfd

Hi, On 07/22/2012 01:27 PM, Pete Batard wrote: > On 2012.07.13 01:27, Pete Batard wrote: >> What will happen then is I'll submit a proposal to this list with all >> the enhancements we talked about sometime next week > > Here we go. > > I'm still not entirely sure disarming the timerfd in handle_t