Contents
How to fix conditional jump or move depends?
To fix that, you may initialize word with NULL as you create a new node. your hash function may return a negative value in case the argument is not an uppercase character and has an ASCII value that is less than 97 (e.g., an apostrophe).
When do you initialize word members in pset5?
The word members that valgrind complains about are those of the 30 nodes that you unnecessarily allocate memory for on line 39. You never initialize the word members of these nodes. Each of these nodes eventually becomes the last node of a chain.
Can a word be initialized with null in pset5?
While the latter might be true, technically there’s no guarantee that word will be equal to NULL because it was never initialized. To fix that, you may initialize word with NULL as you create a new node.
What happens if you have an incorrect value in Valgrind?
If an incorrect value is used as an input to an operation that writes a result, such as an assignment, arithmetic operation or system call, the likely result another incorrect value (a further infection). But this isn’t guaranteed, e.g. if you bitwise-AND an incorrect value with 0, the result is always 0.
Why do I get bogus calls in Valgrind?
The only possible explanations I can think of is either a bug in valgrind itself, or we make bogus VALGRIND_* calls to misinform it about the status of this memory. AFAICT, jemalloc is only place we use VALGRIND_* macros… and I traced all of those and I don’t see any suspicious calls…
Why is Valgrind angry about not initializing a struct?
But I can’t figure out why? valgrind is angry because you never really initialized the member word of your struct pointed to by temp, yet you’re trying to check whether it has NULL as a value. While the latter might be true, technically there’s no guarantee that word will be equal to NULL because it was never initialized.