galapogos wrote: > Thanks. So it's a bug in valgrind? My distribution's version isn't the > latest one. Does the latest version have a fix? Meanwhile how do I suppress > these errors?
I just said that I just committed a fix, so unless somebody has done a release in the last ten minutes when I wasn't looking then no, the latest version does not have a fix. The best fix is probably to use VALGRIND_MAKE_MEM_DEFINED() to mark the result of the ioctl as defined. You will still get a warning about the ioctl itself (though you could do the MAKE_MEM_DEFINED before the ioctl call to avoid that as well) but the other warnings should vanish. > Also, you mention it's a bug concerning ioctl(). What about the other string > functions? Same bug as well? They probably all follow from the bug - the uninitialised result of the ioctl will propagate through code which uses that result. Tom -- Tom Hughes ([email protected]) http://www.compton.nu/ ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
