[Valgrind-users] thread errors on non-threaded program

[Geert F. <gee...@es...>]

hello, i have a monolythic C++ program (3766634 bytes) for which 
valgrind gives errors like beneath. i don't know what these errors mean, 
but i don't trust the threaded stuff in it, since my program is 
non-threaded (i even don't exactly know what a threaded program is, i'm 
guessing that it has to do with forking etc.)

where can i find more information about the origin of the error and the 
error itself (i'm guessing that 15180 is some error code)? did someone 
have the same error? is my program too big? why is the --num-caller not 
working for this error, while it is for others?

thnx,
geert.

valgrind --leak-check=yes --num-callers=30 ./test

==15180== Invalid write of size 1
==15180==    at 0x80C3FDC: GRV::bLoadRVsFromFile(GDLLpGBaseObject*, char 
const*, char const*, bool) (GRV.cpp:346)
==15180==    Address 0xBFB388EF is on thread 1's stack
==15180==
==15180== Invalid write of size 4
==15180==    at 0x80C3FE2: GRV::bLoadRVsFromFile(GDLLpGBaseObject*, char 
const*, char const*, bool) (GRV.cpp:357)
==15180==    Address 0xBFB388E4 is on thread 1's stack