On Sat, 13 Oct 2007, Michael Lamothe wrote: > I have been struggling with application freezes in my application for > about 2 months and I was hoping that I could get some help. I've been > cleaning the application up with errors reported by valgrind but can't > seem to work out what this means. Can anyone shed some light on this? > Should I just ignore this memory error? > > ==13801== Syscall param write(buf) points to uninitialised byte(s) > ==13801== at 0x40007F2: (within /lib/ld-2.5.so) > ==13801== by 0x4B6D64E: _X11TransWrite (in /usr/lib/libX11.so.6.2.0)
I don't think this has anything to do with your application as such. Valgrind is complaining about apparently uninitialized data in regard to XOpenDisplay. Allin Cottrell _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
