Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Libusb fails at initializing (libusb_init) #3047

Closed
Folyz opened this issue Jan 11, 2019 · 3 comments
Closed

Libusb fails at initializing (libusb_init) #3047

Folyz opened this issue Jan 11, 2019 · 3 comments

Comments

@Folyz
Copy link

Folyz commented Jan 11, 2019

Currently I've tried to build and run the realsense-viewer.exe for both the latest version (v2.17.2) as well as an older version v2.16.5. I've done this using Cmake and Visual Studio 2017 (https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_windows.md). In the past I've succesfully compiled and run v2.11.0 with no issues.

Compilation goes fine, however as I start any program that uses the librealsense2.dll such as the realsense viewer it crashes. When compiling in debug mode it gives an access violation at /third-party/libusb/libusb/core.c line 2248:

usbi_backend.clock_gettime(USBI_CLOCK_REALTIME, &timestamp_origin);

I'm guessing the function clock_gettime to which is pointed to is not initialized or something else is wrong, however I couldn't trace back where this error could come from. I've been trying different kind of setups (all windows, visual studio) but I couldn't find the problem, any ideas?

@dorodnic
Copy link
Contributor

Hi @Folyz
I also experienced this yesterday, and what worked for me was modifying GIT_TAG
@ CMake/external_libusb.cmake:8
from master to v1.0.22 (and rebuilding all, by deleting the build folder and re-running CMake) I think something got broken in libusb. We will include the fix in upcoming release, but I hope for now this helps.

@RealSenseCustomerSupport
Copy link
Collaborator

[Please Ignore - RealSense system comment]

@dorodnic
Copy link
Contributor

Should be resolved now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants