Re: [Valgrind-developers] wrong diagnostics off uninitialised value if using incw

[<raf...@gm...>]

On 10/24/06, Julian Seward <js...@ac...> wrote:
>
> Yes, please submit a bug report.  It would also be good to have
> a C program which reproduced the problem, if you can construct
> one.

Just compile the attached files with "g++ -O2 -g main.cpp test.cpp -o
test". It will print the warning

==13355== Conditional jump or move depends on uninitialised value(s)
==13355==    at 0x400568: f(my_s*) (test.cpp:9)
==13355==    by 0x400591: main (main.cpp:11)

With the change you proposed, no warning is printed. Should I submit a
bug report anyway?

> J

Thanks,
Rafael