|
From: Nicholas N. <nj...@ca...> - 2004-03-25 18:51:40
|
On Thu, 25 Mar 2004, Xavier Bestel wrote: > during a valgrind session I stumbled on that (this is the first error): > > ==22013== Invalid read of size 1 > .... > ==22013== Address 0x48C1D128 is not stack'd, malloc'd or free'd > > > When I attach to gdb at this point, and I examine the content of memory > at 0x48C1D128 (to which a char* is pointing), I find a string which > really seems like it has been written by my program. > > How is this possible ? How could my program write to a non stack'd, > malloc'd or free'd address before this point and not been caught by > valgrind ? It does seem a bit strange. Can you write a small example program that shows the problem? N |