Re: windbg digest: February 26, 2003

Thanks Tony,
:o)
You were right and it is the optimization.
One thing I don’t understand though.
I thought that optimization is disabled (\Od)
in checked builds but obviously, it is not so.
My binary just grew 10K.
Care to comment on that discrepancy with DDK?
(MSC_OPTIMIZATION topic)

— Kernel Debugging Interest List digest
wrote:
> WINDBG Digest for Wednesday, February 26, 2003.
>
> 1. I have a weird problem with the stack (symbols)
> 2. RE: I have a weird problem with the stack
> (symbols)
>
>
----------------------------------------------------------------------
>
> Subject: I have a weird problem with the stack
> (symbols)
> From: xxxxx@yahoo.com
> Date: Wed, 26 Feb 2003 20:45:23 -0500
> X-Message-Number: 1
>
> Hello All,
>
> I am stuck on a weird problem that doesn’t let me
> debug the code.
> When I walk through the stack (with F10), I
> consistently jump over
> portions of code (according to stack trace, but not
> really), some
> variables volunterely change values and I cannot put
> breakpoints in some
> places.
> It looks very much like a symbol problem except it
> is more exotic and I
> cannot find what is wrong.
> Can anybody suggest anything?
>
>
----------------------------------------------------------------------
>
> Subject: RE: I have a weird problem with the stack
> (symbols)
> From: Tony Mason
> Date: Wed, 26 Feb 2003 22:17:21 -0500
> X-Message-Number: 2
>
> Is the code in question optimized? If so, keep in
> mind that the flow of
> optimized code may not track well with the final
> assembly code (and if you
> think x86 is bad, you should try following optimized
> IA-64 code…)
>
> Regards,
>
> Tony
>
> Tony Mason
> Consulting Partner
> OSR Open Systems Resources, Inc.
> http://www.osr.com
>
>
> -----Original Message-----
> From: xxxxx@yahoo.com
> [mailto:xxxxx@yahoo.com]
> Sent: Wednesday, February 26, 2003 8:45 PM
> To: Kernel Debugging Interest List
> Subject: [windbg] I have a weird problem with the
> stack (symbols)
>
> Hello All,
>
> I am stuck on a weird problem that doesn’t let me
> debug the code.
> When I walk through the stack (with F10), I
> consistently jump over
> portions of code (according to stack trace, but not
> really), some
> variables volunterely change values and I cannot put
> breakpoints in some
> places.
> It looks very much like a symbol problem except it
> is more exotic and I
> cannot find what is wrong.
> Can anybody suggest anything?
>
> —
> You are currently subscribed to windbg as:
> xxxxx@osr.com
> To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>
>
>
> —
>
> END OF DIGEST
>
> —
> You are currently subscribed to windbg as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
xxxxx@lists.osr.com

__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/

“Gregory Appel” wrote in message news:xxxxx@windbg…
>
> Thanks Tony,
> :o)
> You were right and it is the optimization.
> One thing I don’t understand though.
> I thought that optimization is disabled (\Od)
> in checked builds but obviously, it is not so.
> My binary just grew 10K.
> Care to comment on that discrepancy with DDK?
> (MSC_OPTIMIZATION topic)

You wouldn’t happen to be using the Windows 2000 DDK Checked Build, would
you? The setenv.bat file shipped with that DDK didn’t set the
MSC_OPTIMIZATION properly for the checked build.

Test it by opening a Checked Build Environment, then type:

set msc

If you have a good setup, you will get:
MSC_OPTIMIZATION=/Od /Oi

If it’s bad, you will get:
Environment variable msc not defined

Fix it by editing the Setenv.bat or wrap it in a batch file (or DOSKEY
Macro) that sets MSC_OPTIMIZATION=/Od /Oi after the Setenv.bat file
completes. You can’t set it before you run setenv.bat, because setenv
doesn’t just fail to set it, it unsets it.

Phil

Philip D. Barila
Seagate Technology, LLC
(720) 684-1842
As if I need to say it: Not speaking for Seagate.