From kde-core-devel Tue Apr 23 06:36:04 2002 From: Matthias Welwarsky Date: Tue, 23 Apr 2002 06:36:04 +0000 To: kde-core-devel Subject: Help needed in interpreting valgrind output X-MARC-Message: https://marc.info/?l=kde-core-devel&m=101955330211074 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, valgrinding ksiemens (happens with all other apps, too), I see among other stuff the following output: ==1786== ==1786== Conditional jump or move depends on uninitialised value(s) ==1786== at 0x43DA1112: LiquidStyle::drawPrimitive(QStyle::PrimitiveElement, QPainter *, QRect const &, QColorGroup const &, unsigned int, QStyleOption const &) const (in /opt/kde3_1303/lib/kde3/plugins/styles/liquid.so) ==1786== by 0x43DA6D16: LiquidStyle::drawComplexControl(QStyle::ComplexControl, QPainter *, QWidget const *, QRect const &, QColorGroup const &, unsigned int, unsigned int, unsigned int, QStyleOption const &) const (in /opt/kde3_1303/lib/kde3/plugins/styles/liquid.so) ==1786== by 0x407B5BC1: KToolBarButton::drawButton(QPainter *) (ktoolbarbutton.cpp:519) ==1786== by 0x40D67483: QButton::paintEvent(QPaintEvent *) (in /usr/lib/qt3/lib/libqt-mt.so.3.0.3) I looked into liquid's source code and in drawPrimitive() there's one large switch/case statement, which seems to trigger that warning. However, the switch() is on the QStyle::PrimitiveElement, something that that seems to be delivered by the framework. So, to me it seems the styles are fed with uninitialized values, which may lead to strange behaviour.. Can someone with more knowledge about styles and such have a look and proove me wrong? regards, matze -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8xQDYANO+fpRuZ2IRAlpRAJwJNxeXLCFKPwkWNlnQ7w3Ck8rasACg0fCS jQhJo9W5E9BFTNsYVW5Qew0= =r6Pu -----END PGP SIGNATURE-----