Re: [Valgrind-users] Help understanding error.

[Nicholas N. <nj...@ca...>]

On Wed, 18 Jun 2003, Michael Labhard wrote:

> ==10037== Invalid write of size 4
> ==10037==    at 0x408F3E14: _GLOBAL__I__ZN12MyApp4_ptrE
> (/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2/include/g++-v3/bits/stl_set.h:102)
> ==10037==    by 0x408F72B4: (within
> /home/mel/Projects/src/.libs/libmyapp.so.0.0.0)
> ==10037==    by 0x408C4110: (within
> /home/mel/Projects/src/.libs/libmyapp.so.0.0.0)
> ==10037==    by 0x4000AD4B: call_init (in /lib/ld-2.3.1.so)
> ==10037==    Address 0xBFFFE1C4 is not stack'd, malloc'd or free'd

_GLOBAL__I__ZN12MyApp4_ptrE is not in your code, so there's a good(?)
chance it's not your fault.

Valgrind says "Address 0xBFFFE1C4 is not stack'd, malloc'd or free'd" but
0xBFFFE1C4 looks like a stack address, maybe that code is writing just
beneath the stack pointer.  You could try the --workaround-gcc296-bugs=yes
option which skips that check.  You could also try to reduce the program
to a small example and see if it still happens;  if so you can probably be
more confident that it's not your fault, in which case suppressing it
would be appropriate.

N