Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 04 Jan 2017 13:57:05 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-usb@FreeBSD.org
Subject:   [Bug 215765] libusb_handle_events_completed() hangs after device removal
Message-ID:  <bug-215765-17-Ykrs9Yp2mP@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-215765-17@https.bugs.freebsd.org/bugzilla/>
References:  <bug-215765-17@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215765

Hans Petter Selasky <hselasky@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hselasky@FreeBSD.org

--- Comment #1 from Hans Petter Selasky <hselasky@FreeBSD.org> ---
Hi,

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

env LIBUSB_DEBUG=3D0 program > log0.txt
env LIBUSB_DEBUG=3D1 program > log1.txt
env LIBUSB_DEBUG=3D2 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 CANCEL=
LED
error code. Maybe the pcscd APP doesn't check for this error code?

--HPS

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-215765-17-Ykrs9Yp2mP>