another backtrace (was Re: [BRLTTY] Debugging BRLTTY crashes (Baum driver))

[Samuel Thibault]

Hi,

Jason White, le Sat 12 May 2007 12:48:49 +1000, a écrit :
> Incidentally, from a very quick browse of the latest valgrind output, it
> appears that the warnings about usb_linux.c (lines 275 and 278) are worth
> checking out. If urb isn't guaranteed to be initialized by the ioctl() call
> then it appears that it won't be initialized at all, and line 278 tests
> whether it is non-null.

ioctl() returns 0 only if urb properly got filled. That said,
initializing urb to NULL would let play on the safe side.

As for the warnings for usbReapUrb, they indeed come from a valgrind
bug.

Samuel