PRB: Debugger Displays Incorrect Information for Variable

Last reviewed: July 24, 1997
Article ID: Q168080

The information in this article applies to:

Microsoft Visual C++, 32-bit Editions, version 5.0

SYMPTOMS

When you debug an optimized build of an application that includes debug information, the debugger may display incorrect symbol data.

RESOLUTION

You can work around this problem by displaying the desired variable in a dialog box or printing it out using cout or printf();

MORE INFORMATION

The debugger displays incorrect symbol data when debugging an application built with the following compiler options:

/Oy (Frame-Pointer Omission)
/Og (Global Optimizations)
/Zi or /Z7 (Debug Info)

Steps to Reproduce Behavior

Create a console application that includes the code listed below.

2. Set the active configuration to Release. 3. In the project Settings dialog box, click the C/C++ tab and select

   Program Database in the Debug Info list box.

4. In the Project Settings dialog box, click the Linker tab and select the

   "Generate debug info" check box.

5. Set a breakpoint in Something(). 6. Press the F5 key to build and debug the application.

   //Compiler options needed: /GX /Oy /Og /MLd
   #include <windows.h>
   #include <iostream>

   void Something(DWORD dwFirst, DWORD dwSecond)
   {
      // cout will display the correct information.
      std::cout << "dwFirst = " << dwFirst << ", dwSecond = " << dwSecond
      << std::endl;
   }

   int main()
   {
      DWORD dwFirst = 123456;
      DWORD dwSecond = 234567;

      Something(dwFirst, dwSecond);
      return 0 ;
   }

Keywords : WBDebug
Version : 5.0
Platform : NT WINDOWS
Issue type : kbprb

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 24, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.