Re: WinDbg Variable checking
- From: "Ivan Brugiolo [MSFT]" <ivanbrug@xxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 1 Jul 2005 00:47:42 -0700
or, better
kd> dv /V
so that you have the idea of which variable are possibly aliased by the
compiler
due to optimizations.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Maxim S. Shatskih" <maxim@xxxxxxxxxxxxxxxx> wrote in message
news:O$FGLNdfFHA.2152@xxxxxxxxxxxxxxxxxxxxxxx
> Say "dv"
>
> --
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> maxim@xxxxxxxxxxxxxxxx
> http://www.storagecraft.com
>
> "Denis @ TheOffice" <denisco@xxxxxxx> wrote in message
> news:1120172916.787491@xxxxxxxxxxxxxx
> > Is there like a magic trick to see the content of my variables all I see
is
> the parameters.
> > I can't even see my locals ???
> >
> > Denis
> >
> >
>
>
.
- Follow-Ups:
- Re: WinDbg Variable checking
- From: Denis @ TheOffice
- Re: WinDbg Variable checking
- References:
- WinDbg Variable checking
- From: Denis @ TheOffice
- Re: WinDbg Variable checking
- From: Maxim S. Shatskih
- WinDbg Variable checking
- Prev by Date: 64-bit driver compile error
- Next by Date: Re: Updating public devmode with IPrintOemDriverUI::DrvUpdateUISetting
- Previous by thread: Re: WinDbg Variable checking
- Next by thread: Re: WinDbg Variable checking
- Index(es):
Relevant Pages
|