|
From: Evan B. D. <ebd...@un...> - 2003-09-07 02:58:35
|
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 :) Thanks, Evan Daniel |