Comment # 7 on bug 909567 from Ralf Habacker

(In reply to Johannes Meixner from comment #1)
> With probability one (http://en.wikipedia.org/wiki/Almost_surely)
> when there is a segfault in a glibc library function the root cause
> is not in the library itself but at a higher level somewhere in the
> application that calls library functions in a wrong way (usually by
> calling a library function with an invalid pointer argumet - i.e.
> the caller provides an invalid argumet and that causes the segfault).

I can confirm this: the call to 

  numdev = libusb_get_device_list(NULL, &g_devlist);

does not use the predefined libusb context pointer and should be

  numdev = libusb_get_device_list(g_context, &g_devlist);

which solves the issue.

See https://github.com/Ordissimo/scangearmp2/issues/16 for more details