Re: theoretical MFC question

From:

"Scott McPhillips [MVP]" <org-dot-mvps-at-scottmcp>

Newsgroups:

microsoft.public.vc.mfc

Date:

Mon, 30 Nov 2009 00:30:58 -0500

Message-ID:

<#URdN5XcKHA.2184@TK2MSFTNGP04.phx.gbl>

"Tony C." <me@here.com> wrote in message
news:ddj6h59mvgqbiakojmh0i5nk4s4apkav9t@4ax.com...

I've been debugging like a nutcase for a couple of hours trying to
get the systemtime...

I used

SYSTEMTIME st;
GetSystemTime(&st);

--pretty straighforward....

I'm using unicode, and in building in RELEASE mode....

Release mode is not a problem in VB.net and I can set a watch
on my variables and look inside them any time I want.

So here I am in release mode tyring to check for correct data
in my variables and get Nothing in them ....So I think that
the code isnt working ...

--I pull out my hair for a couple of hours and then decide
to try debug mode...

Then I see everything inside all my variables just fine..

---So my question is :: What's up with that?
Why can't I see inside my variables in release mode?

(Oh yeah, and Plus...there's 2 separate configurations for
debug and release mode that both have to be set correctly !!
One setting will not get both configs...)

I think I'm going to start drinking..... lol!

A release mode compile (with optimizations enabled) moves things around, and
even eliminates some things. The debugger has no way to know where some
variables may be after optimization. And the debugger doesn't know what it
doesn't know, so it can display erroneous results.

To check a variable in release mode you can use OutputDebugString or you can
write to a logging file.

--
Scott McPhillips [VC++ MVP]