|
From: Antti T. <ao...@cc...> - 2006-08-10 16:45:29
|
For some reason, when I run valgrind on a certain (normal) user account I get this feedback from the example program at http://valgrind.org/docs/manual/quick-start.html#quick-start.interpret The program has one modification: i'm trying to write to x[11]. ==19046== Invalid write of size 4 ==19046== at 0x804839F: ??? ==19046== by 0x80483BB: ??? ==19046== by 0x1B938E35: __libc_start_main (in /lib/libc-2.3.2.so) ==19046== by 0x80482E0: ??? ==19046== Address 0x1BA5B054 is 4 bytes after a block of size 40 alloc'd ==19046== at 0x1B90459D: malloc (vg_replace_malloc.c:130) ==19046== by 0x8048395: ??? ==19046== by 0x80483BB: ??? ==19046== by 0x1B938E35: __libc_start_main (in /lib/libc-2.3.2.so) ==19046== by 0x80482E0: ??? ==19046== ==19046== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 13 from 1) ==19046== malloc/free: in use at exit: 40 bytes in 1 blocks. ==19046== malloc/free: 1 allocs, 0 frees, 40 bytes allocated. ==19046== For counts of detected errors, rerun with: -v ==19046== searching for pointers to 1 not-freed blocks. ==19046== checked 77824 bytes. I only get this error when i'm using this certain account. If I use another account, i get ==4002== Invalid write of size 4 ==4002== at 0x804839F: f (valgtest.c:6) ==4002== by 0x80483BB: main (valgtest.c:11) ==4002== Address 0x1BA5B054 is 4 bytes after a block of size 40 alloc'd ==4002== at 0x1B90459D: malloc (vg_replace_malloc.c:130) ==4002== by 0x8048395: f (valgtest.c:5) ==4002== by 0x80483BB: main (valgtest.c:11) from the same binary file, compiled with gcc 3.3.5. Any idea if there is, for example, an enviroment variable or something like that which could cause this? Valgrind version is 2.4.0. -- Antti Tuomi |
|
From: Nicholas N. <nj...@cs...> - 2006-08-11 00:14:56
|
On Thu, 10 Aug 2006, Antti Tuomi wrote: > For some reason, when I run valgrind on a certain (normal) user account > I get this feedback from the example program at > http://valgrind.org/docs/manual/quick-start.html#quick-start.interpret > > The program has one modification: i'm trying to write to x[11]. > > ==19046== Invalid write of size 4 > ==19046== at 0x804839F: ??? > ==19046== by 0x80483BB: ??? > ==19046== by 0x1B938E35: __libc_start_main (in /lib/libc-2.3.2.so) > ==19046== by 0x80482E0: ??? > ==19046== Address 0x1BA5B054 is 4 bytes after a block of size 40 alloc'd > ==19046== at 0x1B90459D: malloc (vg_replace_malloc.c:130) > ==19046== by 0x8048395: ??? > ==19046== by 0x80483BB: ??? > ==19046== by 0x1B938E35: __libc_start_main (in /lib/libc-2.3.2.so) > ==19046== by 0x80482E0: ??? [...] > > Valgrind version is 2.4.0. No idea why, there's nothing that should cause that. You might like to try a more recent version such as 3.2.0. Nick |