Hi,
After more debugging, I believe that the bug I am experiencing is a CUPS
bug rather than one with libusb, but read on.
The system I am working on has no usbfs in kernel, nor udev running.
That means initialisation of the library fails because it can neither
find a usbfs directory nor can it find the right /dev/usb* nodes. If the
caller continues with calling library functions, they eventually cause a
signal 11 due to the library dereferencing a NULL global variable
holding the path to usbfs or the device node.
That means that CUPS is ignoring/mishandling the return value from the
initialisation function and thus has a bug there.
Libusb could use more defensive-style programming and avoid the NULL
dereference even when initialisation has failed, but this is more
debatable as to whether it is a bug.
Let me know if you need more info.
Thanks
Nikos
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
