valgrind: many uninitialised value(s)
Steps to reproduce:
- optional: compile inkscape with debug info on (in cmake set "CMAKE_BUILD_TYPE=Debug", this will help searching for the culprit line of code later on)
- open a console
- run: "valgrind --log-file="inkscape_valgrind.txt" inkscape /tmp/someTest.svg"
- wait for inkscape to appear (be patient, due to valgrind the runtime is very slow, about 1/10)
- use inkscape, draw some lines or just exit inkscape
- open "inkscape_valgrind.txt" in an editor and the results
What happened?
There are many messages such as
- Conditional jump or move depends on uninitialized value(s)
- Use of uninitialized value of size 8
example: inkscape_valgrind.txt example with debug build on: inkscape_dbg_valgrind.txt
What should have happened?
No warnings should appear in the log-file.
These messages show that there is data which is not initialized. The problem with uninitialized values is that it can lead to unpredictable behavior (and/or crashes) and possibly different behavior on different platforms (Windows vs. Linux).
Inkscape Version and Operating System:
- Inkscape Version: Inkscape 1.0alpha (a7aa5701, 2019-03-22, custom)
- Operating System: Linux
- Operating System version: Ubuntu 18.04
Edited by Markus Schwienbacher