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

Jason White jasonw at ariel.its.unimelb.edu.au
Fri May 11 22:48:49 EDT 2007


On Fri, May 11, 2007 at 09:51:55PM -0400, Dave Mielke wrote:
 
> Please retest with the latest revision.

I'll test it with electric fence. If you also want another valgrind report,
let me know.

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.

I know this is tedious, but at some point it would probably be best to go
through all the valgrind warnings to find out which are genuine.



More information about the BRLTTY mailing list