On Wed, Aug 12, 2009 at 3:05 AM, tom fogal<[email protected]> wrote: > >> So with the invalid read, it is trying to read an address that is not >> valid. Would you happen to know what the line "16 bytes inside a >> block 24 free'd" means? > > I think it's telling you where the chunk of memory became invalid. I'd > have to check the docs for the 16 and 24, but maybe the allocator gave > a 24-byte block and the pointer that is invalid points to 16 of them.
You're (illegally) accessing a heap block that has been freed with 'delete'. The block was 24 bytes in size. Your illegal access is 16 bytes from the start of this 24 byte block. See http://www.valgrind.org/docs/manual/mc-manual.html#mc-manual.badrw for more. Nick ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
