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

[Yogesh B. <ybh...@ya...>]

--- "Neulinger, Nathan" <nn...@um...> wrote:
> Sorry, AFS_LWP_STACK_SIZE... it's specific to the afs lwp code to
> change
> the stack size that it uses internally. I raised it to larger than
> 1MB,
> which passes the threshold for memcheck stack switch code.
> 
Ah! OK, I tried a similar option for testbuilder 
(tbvThreadT::setStackSize()) and indeed it made valgrind 
very very quite. Thanx a lot for the tip.

As a side note, it will be great it valgrind had an option to
set the stack size being used by the application, so that if
user knows the stacksize (128K default in case of testbuilder)
she can use the option to inform valgrind.

Is there a formal mechanism to submit a feature request?

Regards,
--
Yogesh



__________________________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo
http://search.yahoo.com