When using vgdb (e.g. `valgrind --vgdb-error=0 myprog`) and there's a valgrind warning for an uninitialized read, on a line like if (a || b)
The question that happens then is, of course, was it a or b that was uninitialized. If one uses vgdb to print the values of a and b, it won't necessarily be obvious (e.g. two bools, both happen to show as "false", with only one actually uninitialized). This makes me wonder, wouldn't it be possible for vgdb to output a warning when doing "print a" or "print b" from gdb and the value is marked as uninitialized? If I understand the architecture correctly, this should be possible to implement, right? -- David Faure | david.fa...@kdab.com | Managing Director KDAB France KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, http://www.kdab.fr KDAB - The Qt, C++ and OpenGL Experts _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users