On Thu, May 03, 2007 at 09:10:18AM -0400, Dave Mielke wrote: > Both this backtrace as well as the last one highlight a call to free() which > has run into trouble. This is an indicator of memory corruption, the most > likely candidate being that the same block has been freed twice. Can you run > brltty with a tool that audits malloc()s and free()s and cause the crash?
I agree with your diagnosis. Which tool would you recommend? Valgrind has been discussed here before as generating false positives. There is also electric fence, and doubtless there are others. _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://mielke.cc/mailman/listinfo/brltty
