> I wonder how many such bugs a memzero()/bzero() will prevent. If the compiler-foo is possible with gcc then a 0 length constant memset warning and a warning if the set value is > 255 would both probably be useful.
Fortunately a lot of other validation/verification tools do pick it up already. Alan -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
