GNOME Bugzilla – Bug 349382
valgrind uninitialized memory warnings setting partly uninitialized X properties
Last modified: 2011-02-04 16:10:38 UTC
Please describe the problem: When starting up Mozilla under valgrind with --sync, I see a few uninitialized memory warnings that are due to bugs in GDK. They're of the "syscall param write(buf) points to uninitialised byte(s)", which is what happens when uninitialized data is sent to the X server. I'll attach a patch (against cvs trunk, and tested against cvs trunk) that fixes two bugs that I actually observed and one that's a case very similar to one of the ones I observed. Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information:
Created attachment 69938 [details] [review] proposed patch
2006-08-15 Matthias Clasen <mclasen@redhat.com> * gdk/x11/gdkdnd-x11.c (gdk_window_register_dnd): * gdk/x11/gdkwindow-x11.c (gdk_window_set_decorations): (gdk_window_set_functions): Zero out some stack-allocated X structures, to avoid valgrind warnings about uninitialized memory. (#349382, David Baron)