It works for me too. Thanks for the hidapi patch @jwrdegoede.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/25#issuecomment-21150497
--
See everything from the browser to
Hi,
I have identified the problem. When libusb_exit() is called, the linux
backend will acquire the linux_hotplug_lock before calling
linux_stop_event_monitor(). In this user's particular case, it looks like
the event monitor thread is seeing activity from udev and then tries to
acquire the linux_
Hi all,
I'm going on vacation for a week starting tomorrow so I don't have time to
look into this myself atm. If anyone has any clues / ideas as to what is going
on here, you're insight is appreciated.
Regards,
Hans
Original Message
Subject: [Bug 985484] New: Deadlock in linu
Well, I managed to get a little more output by also changing -g to -g3 in my
app.
```
[ 6.852191] [6703] libusbx: debug [handle_events] poll() returned 1
[ 6.852199] [6703] libusbx: debug [op_handle_events] checking fd 7 with
revents = 0
nf is disconnected ? ;)
[ 6.852203] [6703] lib
Sorry, I forgot the stacktrace since it so extremely short. I tried recompiling
libusbx with
./configure CC='icc' CXX='icpc' CXXFLAGS='-O3 -g3' CCFLAGS=' -O3 -g3'
but it did not help to get anything more verbose.
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reaso
