Baggy bounds allow axises that are out of bounds, as long as they stay within the specific baggy bounds. One of the causes of the failure of a program is that the baggy bounds system could throw a hard synchronous error if one gets beyond half a slot from the edge of that baggy bound. A few bytes beyond a baggy bound do not cause an error, however, it is out of bounds. A high order bid is set on the pointer so as to prevent one from trying to subsequently dereference the program which will cause a hard fault at that point. Bagginess in bounds does not exist when the bytes are a power of 2. One does not have to instrument every pointer operation if static code analysis can be used to figure out that a particular set of pointer operations is safe (In Jajodia, 2014).
