On 10/02/2016 15:55, Laszlo Ersek wrote: >> > Hmm, not sure why. We're comparing against the inclusive-exclusive >> > range [0,s->vga.vram_size). The right way to check if something is >> > within the range is >= min && < max; the right way to check if something >> > is outside the range is < min || >= max. > Absolutely: if the thing you are verifying against the interval is > itself an inclusive thing, that is, a pixel or byte *drawn*. However, > exactly as you stated in the commit message, for the maximum check, what > we are comparing is the first offset *not* processed.
Right, what my patch does is setting min and max both to pixels that are drawn. Paolo
