On Thu, Nov 11, 2004, Morgan Leah <[EMAIL PROTECTED]> wrote: > I am using a libusb driver for a custom usb hardware > device.
Please use the libusb list instead of the Linux USB lists in the future. > This device is a reel controller unit which will > occassionally need to be recalibrated. I calibrate > when I start using it and then i calibrate a again > whenever it tilts. (Note: the calibration is > mechanical, to the PC the message is just another 64 > byte buffer). > > So I will be moving along spinning the reels and > monitoring their behavior, then I will receive a tilt, > so I will recalibrate. The problem occurs with the > next spin command I send, when I send the first > command to the reels I get a segmentation fault, which > in turn kills my whole program, but the command is > executed. I have been running the program through > Purify from IBM: Rational, and it cannot find any > holes in my code it does however trace a hole to the > usb_interrupt_write(). I have included the output > from purify just below in case anyone can help me > figure out what is wrong. I know that it "shouldn't" > be my code but I am also sure that if there was a bug > in libusb 0.1.8 someone would have noticed it before > now. Any help or ideas on how to resolve this issue > would be wonderful, Thanks > > core dump: > unknown_func [pc=0x40] > usb_interrupt_transfer [linux.o] > usb_interrupt_write [linux.o] > Received signal 11 > ... let me know if you need to see the rest of the > dunp. It is all just SIG_XXX, and it will take a > while to type b/c purify won't let me cut/copy and > paste. usb_interrupt_transfer calls a couple of libc functions and some ioctl's. If it's in an ioctl, then it's likely the buffer passed to libusb is invalid and the signal 11 (SIGSEGV on i386) is generated by the kernel. Unfortunately, I haven't received much feedback about the Interrupt transfer support, but I do know that is being used, so I'm relatively confident it's correct. There have been some changes to the CVS version of libusb, but none that I can think of that would cause a segfault like this. It might be worth trying it however. JE ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
