On Tue, Jun 30, 2009 at 9:42 PM, Steven M. Caesare<scaes...@caesare.com> wrote: > Driver verifier actually allocates pool differently in order to detect > pool allocation errors on boundaries. This by itself is sometimes enough > to avoid the problem, in my experience... although technically the > allocation should still trip the verifier.
Yah, I figured it could be a Heisenbug[1], but I think it's more likely this is just dumb luck, or some kind of inverse application of Murphy's Law -- i.e., what can go wrong, won't, if you actually want it to go wrong. :) In all seriousness, it's only been a couple weeks, so it's early yet in any event. [1] http://www.catb.org/jargon/html/H/heisenbug.html -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
