https://bugzilla.novell.com/show_bug.cgi?id=258742 mvidner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |mvidner@novell.com Status|NEW |ASSIGNED ------- Comment #34 from mvidner@novell.com 2007-04-10 10:20 MST ------- <mvidner> the invalid write at the beginning is worth debugging <HuHa> IIRC that is one of the cases where Qt / Xlib simply copies 8 bytes where only 4 are initialized <HuHa> not really intuitive, but it happens <HuHa> and since it happens in either case, I can't see a connection with that segfault <mvidner> are you sure? ok if that is so then it is probably unrelated <mvidner> i thought that it was overwriting a random memory location <HuHa> IIRC it's the read address where some bytes were never written to <HuHa> not an invalid write address <HuHa> I could be wrong there, though <HuHa> but that's one of the cases we had investigated further a long time ago <mvidner> hm, seems to make sense, "Syscall param writev(vector[...]) points to uninitialised byte(s)" <HuHa> right <mvidner> ok, i will apply more gdb tortu^Winvestigation meanwhile, valgrind refuses to start gdb, grrr. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.