July 2017
Intermediate to advanced
244 pages
6h 33m
English
In short, this is the issue where a variable's value is used without the said variable having been assigned a value. At this point, it's likely that these contents are just whichever bytes were in that part of RAM which just got allocated. As a result, this can lead to unpredictable behavior whenever these contents are used or accessed.
When encountered, Memcheck will throw errors similar to these:
$ valgrind --read-var-info=yes --leak-check=full ./unval==6822== Memcheck, a memory error detector==6822== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.==6822== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info==6822== Command: ./unval==6822== ==6822== Conditional jump or move depends ...
Read now
Unlock full access