|
From: Tyler N. <tyl...@co...> - 2003-09-16 19:01:53
|
Hi, I'm using valgrind to find memory problems in a program that uses libusb. The problem I have is that calls to usb_bulk_read, and usb_control_msg don't "validate" memory. I'm not sure if that's the right word, but use of the memory afterword shows errors for uninitialized memory. I traced down libusb, and these things result as: ioctl(dev->fd, IOCTL_USB_BULK, &bulk) ioctl(dev->fd, IOCTL_USB_CONTROL, &ctrl) My guess is, valgrind doesn't know what these are, or how to handle them. My question, is where do I go from here to resolve this. Currently I'm doing an alternate compile where I memset the memory before the call, this gets rid of the error, but hides anywhere I go past the end of what was read. I hope there is a way I can get valgrind to recognize this correctly. Thanks, -- Tyler Nielsen <tyl...@co...> |