Dillo has been neglecting its valgrind cleanliness recently and it turns out the culprit is dw::Table, which resizes its internal vectors without initialising any new values that appear. If you valgrind dillo and immediately close the splash window, valgrind reports 121 "Conditional jump or move depends on uninitialised value" errors! This patch reduces that number to 2! Regards, Jeremy Henty
On Sun, Mar 02, 2008 at 02:43:56PM +0000, Jeremy Henty wrote:
To explain, these errors appear because the code updates the entries of the cumHeight and colWidths vectors with wrapper methods setCumHeight and setColWidth. These wrappers begin by comparing the new value with old one and branching on the result, so you get the "Conditional jump..." errors whenever the old value was not initialized. That means these errors have nothing to do with any of the Table algorithms, they're entirely due to the way the Table code manages the cumHeight and colWidths vectors. Jeremy Henty
participants (3)
-
jcid＠dillo.org -
Johannes.Hofmann＠gmx.de -
onepoint＠starurchin.org