Bugzilla – Bug 140920
Illegal access in any KDE (any GUI?) program
Last modified: 2006-01-03 18:27:11 UTC
For each tool, which is a KDE application, on startup I get following valgrind error. I have an OpenSuSE 10.0 with any YOU and supplementary packages for KDE, GNOME and misc. It seems to be X11 related, so probably appears also on non-KDE applications? Very likely this will trigger some bug elsewhere, so it should be fixed. This one is from a konqueror start. ==3654== Syscall param writev(vector[...]) points to uninitialised byte(s) ==3654== at 0x41DE986: do_writev (in /lib/tls/libc-2.3.5.so) ==3654== by 0x53412FD: (within /usr/X11R6/lib/libX11.so.6.2) ==3654== by 0x534160E: _X11TransWritev (in /usr/X11R6/lib/libX11.so.6.2) ==3654== by 0x5325394: _XSend (in /usr/X11R6/lib/libX11.so.6.2) ==3654== by 0x53195A2: (within /usr/X11R6/lib/libX11.so.6.2) ==3654== by 0x53197AA: XPutImage (in /usr/X11R6/lib/libX11.so.6.2) ==3654== by 0x4DCD0BF: QPixmap::convertFromImage(QImage const&, int) (in /usr/lib/qt3/lib/libqt-mt.so.3.3.5) ==3654== by 0x4E8B0A6: QPixmap::loadFromData(unsigned char const*, unsigned, char const*, int) (in /usr/lib/qt3/lib/libqt-mt.so.3.3.5) ==3654== by 0x4E8B24C: QPixmap::loadFromData(unsigned char const*, unsigned, char const*, QPixmap::ColorMode) (in /usr/lib/qt3/lib/libqt-mt.so.3.3.5) ==3654== by 0x74E6BC0: (within /opt/kde3/lib/libkhtml.so.4.2.0) ==3654== by 0x73787F7: KHTMLFactory::ref() (in /opt/kde3/lib/libkhtml.so.4.2.0) ==3654== by 0x737885A: KHTMLFactory::KHTMLFactory(bool) (in /opt/kde3/lib/libkhtml.so.4.2.0) ==3654== Address 0x5751724 is 44 bytes inside a block of size 16,384 alloc'd ==3654== at 0x401C71C: calloc (in /usr/lib/valgrind/x86-linux/vgpreload_memcheck.so) ==3654== by 0x5314AE3: XOpenDisplay (in /usr/X11R6/lib/libX11.so.6.2) ==3654== by 0x4DB17AD: qt_init_internal(int*, char**, _XDisplay*, unsigned long, unsigned long) (in /usr/lib/qt3/lib/libqt-mt.so.3.3.5) ==3654== by 0x4DB3F15: qt_init(int*, char**, QApplication::Type) (in /usr/lib/qt3/lib/libqt-mt.so.3.3.5) ==3654== by 0x4E1AF4A: QApplication::construct(int&, char**, QApplication::Type) (in /usr/lib/qt3/lib/libqt-mt.so.3.3.5) ==3654== by 0x4E1B27A: QApplication::QApplication(int&, char**, bool) (in /usr/lib/qt3/lib/libqt-mt.so.3.3.5) ==3654== by 0x4B3445D: KApplication::KApplication(bool, bool) (in /opt/kde3/lib/libkdecore.so.4.2.0) ==3654== by 0x40E8F68: kdemain (in /opt/kde3/lib/libkdeinit_konqueror.so) ==3654== by 0x413CE9F: __libc_start_main (in /lib/tls/libc-2.3.5.so)
this is not an error, but a warning about writing uninitialized data. This happens frequently with all X11 applications and is not a bug.
It is a bug. I would not accept anything like that in our own products. This sort of bug usually produces other issues later time and alltogether is probably one of the reasons, why GUI applications still aren't as stable, as server daemons. This is very likely no KDE (I did not assign this to kde-maintainers), but an X11 problem. It would be nice to at least report this to the correct development group in case nobody at SuSE will fix it. It is much easier for you with DEBUG-info enabled systems, than for me to find, which part of the above list really triggers the error.
it is not a bug. anyway, to make you believe that everything is okay, I added a suppression, so that it will still happen, but it won't be reported anymore.