[Bug 215765] libusb_handle_events_completed() hangs after device removal

2017-01-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215765

--- Comment #2 from Hans Petter Selasky  ---
Hi,

Also try to attach to the hung process using "gdb -p proc_number" and enter
"bt" to get a backtrace. It will be helpful.

--HPS

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"


[Bug 215765] libusb_handle_events_completed() hangs after device removal

2017-01-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215765

Hans Petter Selasky  changed:

   What|Removed |Added

 CC||hsela...@freebsd.org

--- Comment #1 from Hans Petter Selasky  ---
Hi,

Can you set the LIBUSB_DEBUG environment before running the USB application?

env LIBUSB_DEBUG=0 program > log0.txt
env LIBUSB_DEBUG=1 program > log1.txt
env LIBUSB_DEBUG=2 program > log2.txt

And reproduce the issue?

libusb_handle_events_completed() only returns when the *completed variable is
set to non-zero, typically when the USB transfer callbacks receive a CANCELLED
error code. Maybe the pcscd APP doesn't check for this error code?

--HPS

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"