|
From: Nicholas N. <nj...@ca...> - 2003-09-15 09:40:03
|
On Sat, 6 Sep 2003, Evan Berggren Daniel wrote: > Is there a way to make valgrind not decide that the program has switched > stacks? I have a program that allocates a lot on the stack as main() > initializes, which causes valgrind to think the program has switched > stacks; this then causes spurious errors. I have since changed the > program to work around this, and valgrind is working fine, but it seems > there should be some sort of option for when you know the client program > won't switch stacks. If there is none, then count this as a feature > request :) The quick hacky way is to adjust the value of VG_PLAUSIBLE_STACK_SIZE in coregrind/vg_memory.c. N |