RE: [Valgrind-users] not understanding some valgrind errors against afs...

[Nicholas N. <nj...@ca...>]

On Tue, 15 Apr 2003, Neulinger, Nathan wrote:

> I think (from what I understand) that the problem is that if you lower
> the threshold to something like 128K, valgrind will get confused if you
> allocate a 128K+ object on the stack. If you're certain that no
> individual object on the stack would be that size, it would probably be
> useful to have an option to specify it.

Would a client request be a good compromise?  Eg.  insert
VALGRIND_STACK_SWITCH just before the stack switch?  It's more intrusive
than a command line option, but it's more precise.  Similar to the client
request for handling self-modifying code.

[I haven't thought through how the request would actually be implemented,
 but it shouldn't be too hard, I think...]

N