Hi Again,
I just tried running inkscape in linux with valgrind for the first time ever, and it reveals some interesting results (attached). It seems that libgc's malloc function has a bug where the library will operate using uninitialised data.
"Conditional jump or move depends on uninitialised value(s)"
It might be quite cool to have a bit of a proper play with valgrind. It seems really quite hi-tech, and I'm hopeful it will be able to reveal quite a few memory related bugs.
Joel
On Wed, 16 Jan 2008 23:10:51 +0000, Joel Holdsworth <joel@...1709...> wrote:
Hi Again,
I just tried running inkscape in linux with valgrind for the first time ever, and it reveals some interesting results (attached). It seems that libgc's malloc function has a bug where the library will operate using uninitialised data.
"Conditional jump or move depends on uninitialised value(s)"
This is not a bug but a necessary consequence of it being a conservative collector. I think there is a .supp file in the Inkscape tree which I created for use with libgc so that the spurious uninitialized warnings from libgc don't obscure other problems, although I don't know how up-to-date it is.
What version of libgc are you using? For a while, recent libgc versions were incompatible with valgrind, leading to a crash. I would be gratified to learn that newer versions are compatible again...
-mental
participants (2)
-
Joel Holdsworth -
MenTaLguY