This is being tracked at https://bugs.kde.org/show_bug.cgi?id=205241#c80
J On Wednesday, July 14, 2010, Dave MacLachlan wrote: > ... > --33662:0:aspacem 571: file 0116c68000-011aaf7fff 62m r-xT- SmFixed > d=0x12b0f1e4 i=639 o=85987328 (148) m=0 /dev/ttys002 > --33662:0:aspacem ...: .... 01197c5000-0119bc4fff 4194304 rwx.. ....... > d=0x000 i=0 o=0 (.) m=. (none) > --33662:0:aspacem segment mismatch: V's seg 1st, kernel's 2nd: > --33662:0:aspacem 571: file 0116c68000-011aaf7fff 62m r-xT- SmFixed > d=0x12b0f1e4 i=639 o=85987328 (148) m=0 /dev/ttys002 > --33662:0:aspacem ...: .... 0119bc5000-0119fc4fff 4194304 rwx.. ....... > d=0x000 i=0 o=0 (.) m=. (none) > --33662:0:aspacem segment mismatch: V's seg 1st, kernel's 2nd: > --33662:0:aspacem 571: file 0116c68000-011aaf7fff 62m r-xT- SmFixed > d=0x12b0f1e4 i=639 o=85987328 (148) m=0 /dev/ttys002 > --33662:0:aspacem ...: .... 0119fc5000-0119fc5fff 4096 ---.. ....... > d=0x000 i=0 o=0 (.) m=. (none) > --33662:0:aspacem segment mismatch: V's seg 1st, kernel's 2nd: > --33662:0:aspacem 571: file 0116c68000-011aaf7fff 62m r-xT- SmFixed > d=0x12b0f1e4 i=639 o=85987328 (148) m=0 /dev/ttys002 > --33662:0:aspacem ...: .... 0119fc6000-011a047fff 532480 rw-.. ....... > d=0x000 i=0 o=0 (.) m=. (none) > --33662:0:aspacem segment mismatch: V's seg 1st, kernel's 2nd: > --33662:0:aspacem 571: file 0116c68000-011aaf7fff 62m r-xT- SmFixed > d=0x12b0f1e4 i=639 o=85987328 (148) m=0 /dev/ttys002 > --33662:0:aspacem ...: .... 011a048000-011a447fff 4194304 rwx.. ....... > d=0x000 i=0 o=0 (.) m=. (none) > --33662:0:aspacem segment mismatch: V's seg 1st, kernel's 2nd: > --33662:0:aspacem 571: file 0116c68000-011aaf7fff 62m r-xT- SmFixed > d=0x12b0f1e4 i=639 o=85987328 (148) m=0 /dev/ttys002 > --33662:0:aspacem ...: .... 011a448000-011a847fff 4194304 rwx.. ....... > d=0x000 i=0 o=0 (.) m=. (none) > --33662:0:aspacem segment mismatch: V's seg 1st, kernel's 2nd: > --33662:0:aspacem 571: file 0116c68000-011aaf7fff 62m r-xT- SmFixed > d=0x12b0f1e4 i=639 o=85987328 (148) m=0 /dev/ttys002 > --33662:0:aspacem ...: .... 011a848000-011ac10fff 3969024 rwx.. ....... > d=0x000 i=0 o=0 (.) m=. (none) > --33662:0:aspacem sync check at wqthread_hijack:0 (after): FAILED > > While running valgrind on my app, I'm seeing a pile of these. Could > somebody be kind enough to explain what it means to me, and is it > something I need to fix? > > Cheers, > Dave ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
