Re: [Valgrind-developers] confusing Memcheck message: Uninitialised value was created by a stack allocation

[Nicholas N. <n.n...@gm...>]

On Tue, May 19, 2009 at 6:58 PM, Konstantin Serebryany
<kon...@gm...> wrote:
>> I think the current behaviour is reasonable.  The stack memory is
>> allocated upon entry to the function;  if you have more than one stack
>> variable they will be allocated all at once, not one at a time.
>> Because of this, the debug info, which Valgrind relies on, identifies
>> the stack allocation with the opening brace of the function, which is
>> often on its own line but in your example is on the same line as the
>> declaration for main().
>
> That is right. But not every memcheck user understands that.
> I just suggested to make the report phrase a bit more descriptive.

I would be reluctant to make an accurate message less accurate in
order to address a user's lack of knowledge about how stack frames
work.

Nick