|
From: Julian S. <js...@ac...> - 2009-02-06 19:08:09
|
On Friday 06 February 2009, Ross Boylan wrote: > On Fri, 2009-02-06 at 19:47 +0100, Julian Seward wrote: > > > invalid read. However, there is no indication of why it is invalid. > > > > Um, it says it is invalid because you are reading freed memory: > > I believe those are 2 separate error reports. The addresses are > different, and the indentation seems to indicate they are distinct > items. What you have here is one single error report, with two stacks. It's unfortunate that Valgrind's text output is sometimes so verbose, so it's hard to see the boundaries of each error. Errors are separated by a line containing only "==PID==" and nothing else, and you'll find there are no such in what you pasted in. I was just thinking, it is unfortunate these errors are so verbose. One solution is to use the Valkyrie GUI to display the errors (available at http://valgrind.org/downloads). This makes it much easier to see where the error boundaries are, and also much easier to navigate the Memcheck output for large programs. J |