Specify the module name in the Watch dialog box. I use something like this:
FgPeer!fDx to display the local instance of the function DO extension.
Gary G. Little
Sr. Staff Engineer
Broadband Storage, LLC
xxxxx@broadstor.com
xxxxx@delphieng.com
-----Original Message-----
From: John Hirschi [mailto:xxxxx@SonicWALL.com]
Sent: Thursday, March 01, 2001 1:16 PM
To: NT Developers Interest List
Subject: [ntdev] AAAAAHHHH!! Locals getting trampled (windbg problem?)
Hi,
I am using WindBg to debug my driver and I have been seeing some
unexpected behavior. Sometimes when I step into a function, one or more
of the local variables aren’t displayed in the “Locals” window. I tried
bringing up their value in the “Watch” window, but I usually get “Error
: Cannot get value”. My only guess is that they are being optimized
out. But I am building a checked build, I assumed that all
optimizations would be off.
Normally I wouldn’t write about something like this, I’d just put in
some debug statements and bow before my Microsoft shrine and thank it
that I have debug statements. But I’ve noticed that some of my local
variables get assigned the same address as the arguments for the
function they are in. As soon as one of my locals gets assigned a
value, the function argument gets set to that value, too! I’ll have a
seemingly innocuous statement like j = 0; and 3 out of my 5 locals get
set to zero.
My Help | About says I am using Microsoft WinDbg:2.0.0023.0 Version 5.0
(Build 2195: Service Pack 1).
Can you please give me a suggestion for a solution?
Thanks
John
You are currently subscribed to ntdev as: xxxxx@delphieng.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com