chromatic wrote: > In theory, this patch should apply and run cleanly. It doesn't. > > Thus, something somewhere pokes into memory it shouldn't. > > Any ideas? Alternately, any comments on this analysis?
I think adding memory checks is a brilliant idea, especially because memory is sometimes recycled with GC, thus malloc/free checks being less useful. The bug where a PMC was still used while already being put on the free list, and aggravated by the fact that the free list pointer is put at the same address as the data comes into mind. I really like what Microsoft has done with their memory guards. The Structure of a Page Heap Block http://msdn2.microsoft.com/en-us/library/ms220938(vs.80).aspx It would be great if someone could have a look at patches 43432 and 43529. They might be memory relevant too. Ron
