2008-02-16 00:12:00 UTC
i've been using windbg for a while now and am still getting used to it
and its commands. Recently when debugging a driver , a WDM driver compiled
with WDK 6000 I got a strange issue of loosing context of local variables.
i.e when stepping through parameters passed to certain functions becomes
null and not all of the local variables are listed in the locals window. and
another strange thing I noted was that in one function the memory location
of some local variables showed by windbg's local window is same location
even though those variables are not even of the same type.
This is not an issue with the driver as it is working correctly and I
overcame the limitation through making temporary global variables that I
accessed using watch. is this known limitation or any of u came across this
issue ? I am using the latest version of windbg and this issue appeared only
after I started to use the latest version of windbg