Comments on: Eliminating undefined values with Valgrind, the easy way http://blog.mozilla.com/nnethercote/2009/02/27/eliminating-undefined-values-with-valgrind-the-easy-way/ Mon, 13 Feb 2012 14:54:05 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: pinotree http://blog.mozilla.com/nnethercote/2009/02/27/eliminating-undefined-values-with-valgrind-the-easy-way/comment-page-1/#comment-34 pinotree Sun, 01 Mar 2009 14:58:08 +0000 http://blog.mozilla.com/nnethercote/?p=42#comment-34 > And just think, if C++ warned about fields uninitialised by constructors, I think adding -Weffc++ to the CXXFLAGS should help about that. > And just think, if C++ warned about fields uninitialised by constructors,

I think adding -Weffc++ to the CXXFLAGS should help about that.

]]> By: Snark http://blog.mozilla.com/nnethercote/2009/02/27/eliminating-undefined-values-with-valgrind-the-easy-way/comment-page-1/#comment-33 Snark Sun, 01 Mar 2009 09:23:13 +0000 http://blog.mozilla.com/nnethercote/?p=42#comment-33 The valgrind I'm using already advertizes the --track-origin feature in the error summary : ==13541== Use --track-origins=yes to see where uninitialised values come from The valgrind I’m using already advertizes the –track-origin feature in the error summary :
==13541== Use –track-origins=yes to see where uninitialised values come from

]]> By: Nik http://blog.mozilla.com/nnethercote/2009/02/27/eliminating-undefined-values-with-valgrind-the-easy-way/comment-page-1/#comment-32 Nik Sun, 01 Mar 2009 04:46:33 +0000 http://blog.mozilla.com/nnethercote/?p=42#comment-32 Jesse, --track-origins is advertised at the end if you have any undefinedness warnings: ==9370== Memcheck, a memory error detector. ==9370== Copyright (C) 2002-2008, and GNU GPL'd, by Julian Seward et al. ==9370== Using LibVEX rev 1668, a library for dynamic binary translation. ==9370== Copyright (C) 2004-2008, and GNU GPL'd, by OpenWorks LLP. ==9370== Using valgrind-3.5.0.SVN, a dynamic binary instrumentation framework. ==9370== Copyright (C) 2000-2008, and GNU GPL'd, by Julian Seward et al. ==9370== For more details, rerun with: -v ==9370== ==9370== Conditional jump or move depends on uninitialised value(s) ==9370== at 0x40056A: main (badloop.c:12) ==9370== ==9370== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 8 from 1) ==9370== malloc/free: in use at exit: 0 bytes in 0 blocks. ==9370== malloc/free: 0 allocs, 0 frees, 0 bytes allocated. ==9370== For counts of detected errors, rerun with: -v ==9370== Use --track-origins=yes to see where uninitialised values come from ==9370== All heap blocks were freed -- no leaks are possible. We could do it for every undefinedness warning, but there's a trade-off between user education and obnoxiousness :) Jesse, –track-origins is advertised at the end if you have any undefinedness warnings:

==9370== Memcheck, a memory error detector.
==9370== Copyright (C) 2002-2008, and GNU GPL’d, by Julian Seward et al.
==9370== Using LibVEX rev 1668, a library for dynamic binary translation.
==9370== Copyright (C) 2004-2008, and GNU GPL’d, by OpenWorks LLP.
==9370== Using valgrind-3.5.0.SVN, a dynamic binary instrumentation framework.
==9370== Copyright (C) 2000-2008, and GNU GPL’d, by Julian Seward et al.
==9370== For more details, rerun with: -v
==9370==
==9370== Conditional jump or move depends on uninitialised value(s)
==9370== at 0x40056A: main (badloop.c:12)
==9370==
==9370== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 8 from 1)
==9370== malloc/free: in use at exit: 0 bytes in 0 blocks.
==9370== malloc/free: 0 allocs, 0 frees, 0 bytes allocated.
==9370== For counts of detected errors, rerun with: -v
==9370== Use –track-origins=yes to see where uninitialised values come from
==9370== All heap blocks were freed — no leaks are possible.

We could do it for every undefinedness warning, but there’s a trade-off between user education and obnoxiousness :)

]]> By: Jesse Ruderman http://blog.mozilla.com/nnethercote/2009/02/27/eliminating-undefined-values-with-valgrind-the-easy-way/comment-page-1/#comment-31 Jesse Ruderman Sat, 28 Feb 2009 08:24:31 +0000 http://blog.mozilla.com/nnethercote/?p=42#comment-31 Maybe the "Conditional jump or move depends on uninitialised value(s)" warning should advertise the --track-origins feature, in the same way the leak summary advertises the --leak-check feature. It would be nice if the error message distinguished jumps from moves. Maybe the “Conditional jump or move depends on uninitialised value(s)” warning should advertise the –track-origins feature, in the same way the leak summary advertises the –leak-check feature.

It would be nice if the error message distinguished jumps from moves.

]]> By: Benjamin Smedberg http://blog.mozilla.com/nnethercote/2009/02/27/eliminating-undefined-values-with-valgrind-the-easy-way/comment-page-1/#comment-30 Benjamin Smedberg Fri, 27 Feb 2009 13:55:47 +0000 http://blog.mozilla.com/nnethercote/?p=42#comment-30 We can very easily generate warnings about uninitialized fields in constructors using our static analysis toolchain. Feel free to file a bug. We can very easily generate warnings about uninitialized fields in constructors using our static analysis toolchain. Feel free to file a bug.

]]>