valgrind reported uninitialized value issues
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
In Progress
|
Undecided
|
David Mathog |
Bug Description
As reported here
http://
valgrind has been showing
Conditional jump or move depends on uninitialised value(s)
messages on tests like this:
valgrind -v --leak-check=yes --leak-
The patch (next message) resolves 3 of these. Two are in style.cpp and one is in sp-clippath.cpp. Note that swapping the bit order in SPILengthOrNormal so that the first 3 fields matched those in SPILength resolved the vast majority of the style.cpp warnings. That issue was mentioned here:
http://
before I discovered that making the field order switch resolved the uninitialized variable warnings.
Even after the patch there is still one remaining warning of this type coming out of Inkscape code (and a few more from libraries Inkscape calls). The one Inkscape one is:
==9481== Conditional jump or move depends on uninitialised value(s)
==9481== at 0x551D121: ??? (in /usr/lib/
==9481== by 0x5524FE4: g_signal_
==9481== by 0x5525442: g_signal_emit (in /usr/lib/
==9481== by 0x46CA2B6: ??? (in /usr/lib/
==9481== by 0x46E194F: gtk_window_
==9481== by 0x46E46B3: ??? (in /usr/lib/
==9481== by 0x42A5724: Gtk::Widget_
==9481== by 0x45908A1: ??? (in /usr/lib/
==9481== by 0x945D397: ???
==9481== Uninitialised value was created by a heap allocation
==9481== at 0x402BE68: malloc (in /usr/lib/
==9481== by 0x8413A00: SPDesktopWidget
==9481== by 0x8413E1F: sp_desktop_
==9481== by 0x80FFD68: sp_file_
==9481== by 0x80AD85D: sp_main_gui(int, char const**) (main.cpp:1087)
==9481== by 0x808BDB0: main (main.cpp:812)
tags: | added: code-design |
Changed in inkscape: | |
status: | New → In Progress |
assignee: | nobody → David Mathog (mathog) |
The one remaining problem of this type wholly within Inkscape is found at around line 580 in the attached file.