local varibles

WINDBG
1

I could not see all local variables in Locals view.
If I give Mydriver!variable1 on Watch window, still I am not able to see.
Can somebody help me?

Thanks
Ramaraj

You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

2

This could be a couple of things:

First you need to have correct symbols loaded for the module you
want to see locals in. It also needs to be a PDB symbol file as locals
are currently not supported with the older symbol file formats. And of
course you will not be able to see locals for modules from Windows as we
don’t provide that info in the symbols we hand out. You can
troubleshoot symbol loading problems with “!sym noisy”. See the docs
for more info.

Second is that if you code is optimized then local behavior
becomes somewhat undefined. This is because the compiler plays all
sorts of tricks when optimizing and does not provide complete
information in the symbol file as to what it did. Typical results are
missing locals (compiler optimized the variable away) and locals with
wrong values (compiler merged the memory location with another local).
Mapping memory contents to source code in optimized code is not
something that any debugger can do because of the lack of information
provided by the compiler.

-----Original Message-----
From: Ramaraj Pandian [mailto:xxxxx@dvdjukebox.com]
Sent: Friday, August 03, 2001 10:32 AM
To: Kernel Debugging Interest List
Subject: [windbg] local varibles

I could not see all local variables in Locals view.
If I give Mydriver!variable1 on Watch window, still I am not able to
see.
Can somebody help me?

Thanks
Ramaraj

You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

3

Thanks Nathan. Looks like mine is second one. How do I solve.
I use MSC_WARNING_LEVEL=/FR /WX
C_DEFINES= -DUNICODE -DMDL_64_BIT_VA, thats all in sources.

Thanks
Ramaraj

-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@windows.microsoft.com]
Sent: Friday, August 03, 2001 11:49 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: local varibles

This could be a couple of things:

First you need to have correct symbols loaded for the module you
want to see locals in. It also needs to be a PDB symbol file as locals
are currently not supported with the older symbol file formats. And of
course you will not be able to see locals for modules from Windows as we
don’t provide that info in the symbols we hand out. You can
troubleshoot symbol loading problems with “!sym noisy”. See the docs
for more info.

Second is that if you code is optimized then local behavior
becomes somewhat undefined. This is because the compiler plays all
sorts of tricks when optimizing and does not provide complete
information in the symbol file as to what it did. Typical results are
missing locals (compiler optimized the variable away) and locals with
wrong values (compiler merged the memory location with another local).
Mapping memory contents to source code in optimized code is not
something that any debugger can do because of the lack of information
provided by the compiler.

-----Original Message-----
From: Ramaraj Pandian [mailto:xxxxx@dvdjukebox.com]
Sent: Friday, August 03, 2001 10:32 AM
To: Kernel Debugging Interest List
Subject: [windbg] local varibles

I could not see all local variables in Locals view.
If I give Mydriver!variable1 on Watch window, still I am not able to
see.
Can somebody help me?

Thanks
Ramaraj

You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to windbg as: xxxxx@dvdjukebox.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

4

Doing a checked build should produce an unoptimized binary.

However keep in mind that there was a DDK release where the chk build
environment would produce optimized binaries. Searching the list
archives should yield more info about this and the KB article on it with
the workaround.

If you want to directly modify your sources file to produce an
unoptimized build then you will have to look at your compiler
documentation for the right flags.

-----Original Message-----
From: Ramaraj Pandian [mailto:xxxxx@dvdjukebox.com]
Sent: Friday, August 03, 2001 11:59 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: local varibles

Thanks Nathan. Looks like mine is second one. How do I solve.
I use MSC_WARNING_LEVEL=/FR /WX
C_DEFINES= -DUNICODE -DMDL_64_BIT_VA, thats all in sources.

Thanks
Ramaraj

-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@windows.microsoft.com]
Sent: Friday, August 03, 2001 11:49 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: local varibles

This could be a couple of things:

First you need to have correct symbols loaded for the module you
want to see locals in. It also needs to be a PDB symbol file as locals
are currently not supported with the older symbol file formats. And of
course you will not be able to see locals for modules from Windows as we
don’t provide that info in the symbols we hand out. You can
troubleshoot symbol loading problems with “!sym noisy”. See the docs
for more info.

Second is that if you code is optimized then local behavior
becomes somewhat undefined. This is because the compiler plays all
sorts of tricks when optimizing and does not provide complete
information in the symbol file as to what it did. Typical results are
missing locals (compiler optimized the variable away) and locals with
wrong values (compiler merged the memory location with another local).
Mapping memory contents to source code in optimized code is not
something that any debugger can do because of the lack of information
provided by the compiler.

-----Original Message-----
From: Ramaraj Pandian [mailto:xxxxx@dvdjukebox.com]
Sent: Friday, August 03, 2001 10:32 AM
To: Kernel Debugging Interest List
Subject: [windbg] local varibles

I could not see all local variables in Locals view.
If I give Mydriver!variable1 on Watch window, still I am not able to
see.
Can somebody help me?

Thanks
Ramaraj

You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to windbg as: xxxxx@dvdjukebox.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com