|
From: Nicholas N. <nj...@ca...> - 2004-08-07 15:41:43
|
On Sat, 7 Aug 2004 bv...@bv... wrote: >> What's happening is that the very large array is using about 1Mb of >> stack space and that is confusing valgrind into thinking that the >> thread has switched to a different stack so it doesn't mark all that >> space as writable and then you get invalid write warnings. > > Then is this a bug? Should I submit a bug report? It is a bug, it's already in the database (bugs.kde.org/show_bug.cgi?id=81361). Nobody's come up with a satisfactory solution yet, however. As a temporary workaround, make VG_PLAUSIBLE_STACK_SIZE in coregrind/vg_memory.c bigger, and recompile... N |