Created attachment 120734 [details] [review]
apitrace patch for honoring range in DrawRangeElementsX commands

So you'd want something like this (totally untested) patch for apitrace?
Makes sense I guess that the specified range not only means the supplied
indices have to be inside that range, but it also works the other way round
(driver can rely on the specified range being accessible) - otherwise the
driver would still need to scan the actual index buffer. (Albeit since for this
app the ranges seem to be pretty bogus who knows if the memory inside the
specified range but not used in the actual indices is really always
accessible.)
I am actually wondering if it would be legal if the memory isn't accessible
below the start value (apitrace surely couldn't handle that)...