Also a problem in version 1.3 of niemiro.dll; let us know what you find and what type of corruption caused it. I'm curious now. :-}
Usually what happens is the app identifies addresses for the rawstack - but the incorrect addresses due to the corruption.
It then starts at one end and works towards the other, but if the address are massively far apart (one of them often being 0), it takes ages and appears to hang the app. Technically, if you leave it long enough (often several hours), it might recover.
I need to implement a system to catch when the addresses are too far apart. But I don't know what value to give it. Some rawstack output can be really long. And even if I set it at something safe like 10,000, it will hang for many minutes, as the WinDBG lookup of memory via symbols and all the other craziness it does is really slow.
I don't know what to do really.
Anyway, I will identify a way to spot this type of corruption and add a conditional for it.
Richard
