REing a binary and while its running (using Windbg by the way) my (call)stack gets mangled. So I start to perform a stack trace [https://msdn.microsoft.com/en-us/library/windows/hardware/ff552143(v=vs.85).aspx].
However, when I'm verifying various symbols/functions in the target, various instructions are paged out so I cant tell if the previous instruction was a ret or a call above it, e.g.
kd> u fe682ae4-2 l1 // paged out (all zeroes) unknown rdr!_RdrSectionInfo+0x2a: fe682ae2 0000 add [eax],al
I know how to reload symbols via !vad extension [https://msdn.microsoft.com/en-us/library/windows/hardware/ff552153(v=vs.85).aspx]. However, that requires me to use (live)kd.
Is there an easier way to ensure the target application doesn't get paged out, short of disabling the pagefile?
I've searched Google, OSRonline, Woodmann, etc. and haven't found anything helpful.