Skip to content

Commit cf4fca3

Browse files
author
Colin Robertson
authored
Merge pull request #3947 from MicrosoftDocs/main637897052150478443
Repo sync for protected CLA branch
2 parents 7a731cc + 51d3c77 commit cf4fca3

File tree

5 files changed

+113
-83
lines changed

5 files changed

+113
-83
lines changed
Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
description: "Learn more about: /Zo (Enhance Optimized Debugging)"
33
title: "/Zo (Enhance Optimized Debugging)"
4-
ms.date: "11/04/2016"
4+
ms.date: 06/01/2022
55
f1_keywords: ["-Zo", "/Zo"]
66
helpviewer_keywords: ["Zo compiler option [C++]", "/Zo compiler option [C++]", "-Zo compiler option [C++]"]
77
ms.assetid: eea8d89a-7fe0-4fe1-86b2-7689bbebbd7f
@@ -12,17 +12,17 @@ Generate enhanced debugging information for optimized code in non-debug builds.
1212

1313
## Syntax
1414

15-
```cpp
16-
/Zo[-]
17-
```
15+
> **`/Zo`**\[**`-`**]
1816
1917
## Remarks
2018

21-
The **/Zo** compiler switch generates enhanced debugging information for optimized code. Optimization may use registers for local variables, reorder code, vectorize loops, and inline function calls. These optimizations can obscure the relationship between the source code and the compiled object code. The **/Zo** switch tells the compiler to generate additional debugging information for local variables and inlined functions. Use it to see variables in the **Autos**, **Locals**, and **Watch** windows when you step through optimized code in the Visual Studio debugger. It also enables stack traces to show inlined functions in the WinDBG debugger. Debug builds that have disabled optimizations ([/Od](od-disable-debug.md)) do not need the additional debugging information generated when **/Zo** is specified. Use the **/Zo** switch to debug Release configurations with optimization turned on. For more information on optimization switches, see [/O Options (Optimize Code)](o-options-optimize-code.md). The **/Zo** option is enabled by default in Visual Studio when you specify debugging information with **/Zi** or **/Z7**. Specify **/Zo-** to explicitly disable this compiler option.
19+
The **`/Zo`** compiler option generates enhanced debugging information for optimized code. Optimization may use registers for local variables, reorder code, vectorize loops, and inline function calls. These optimizations can obscure the relationship between the source code and the compiled object code. The **`/Zo`** option tells the compiler to generate extra debugging information for local variables and inlined functions. It allows you to see variables in the **Autos**, **Locals**, and **Watch** windows when you step through optimized code in the Visual Studio debugger. It also enables stack traces to show inlined functions in the WinDBG debugger. Debug builds that have disabled optimizations ([`/Od`](od-disable-debug.md)) don't need the extra debugging information generated when **`/Zo`** is specified. Use the **`/Zo`** option to debug Release configurations with optimization turned on. For more information on optimization options, see [`/O` options (Optimize Code)](o-options-optimize-code.md).
2220

23-
The **/Zo** switch is available starting in Visual Studio 2013 Update 3, and it replaces the previously undocumented **/d2Zi+** switch.
21+
The **`/Zo`** option is enabled by default when you specify debugging information with **`/Zi`** or **`/Z7`**. It's disabled by the **`/ZI`** compiler option. Specify **`/Zo-`** to explicitly disable this compiler option.
2422

25-
### To set the /Zo compiler option in Visual Studio
23+
The **`/Zo`** option is available starting in Visual Studio 2013 Update 3, and it replaces the previously undocumented **`/d2Zi+`** option.
24+
25+
### To set the `/Zo` compiler option in Visual Studio
2626

2727
1. Open the **Property Pages** dialog box for the project. For more information, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
2828

@@ -36,6 +36,6 @@ The **/Zo** switch is available starting in Visual Studio 2013 Update 3, and it
3636

3737
## See also
3838

39-
[/O Options (Optimize Code)](o-options-optimize-code.md)<br/>
40-
[/Z7, /Zi, /ZI (Debug Information Format)](z7-zi-zi-debug-information-format.md)<br/>
39+
[`/O` Options (Optimize code)](o-options-optimize-code.md)\
40+
[`/Z7`, `/Zi`, `/ZI` (Debug information format)](z7-zi-zi-debug-information-format.md)\
4141
[Edit and Continue](/visualstudio/debugger/edit-and-continue)

docs/code-quality/c1252.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,18 @@
11
---
22
description: "Learn more about: C1252"
33
title: C1252
4-
ms.date: 11/04/2016
4+
ms.date: 06/01/2022
55
ms.topic: reference
66
f1_keywords: ["C1252"]
77
helpviewer_keywords: ["C1252"]
88
ms.assetid: e88bf199-890d-4582-bb5c-c1238797145b
99
---
1010
# C1252
1111

12-
> warning C1252: Circular or missing dependency between plugins: requires GUID
12+
> warning C1252: Circular or missing dependency between plugins: '*plugin-name*' requires GUID '*globally-unique-identifier*'
1313
14-
The Code Analysis tool reports this warning when there is an internal error with plugin dependencies, not in the code being analyzed.
14+
The Code Analysis tool reports this warning when there's an internal error in the plugin dependencies. It's not caused by an issue in the code being analyzed.
15+
16+
In some cases, it's possible to work around this issue by disabling the **Enable Code Analysis on Build** property. To disable this build property, open the Property pages dialog for your project. In the **Solution Explorer** window, right-click on the project (not the solution) and select **Properties** in the shortcut menu. Set the **Configuration** to **All Configurations** and the **Platform** to **All Platforms**. Open the **Configuration Properties** > **Code Analysis** > **General** property page. Modify the **Enable Code Analysis on Build** property to **No**. Choose **OK** to save your changes, and then save your project files. Rebuild your project to verify that the issue no longer occurs.
17+
18+
If the issue continues, you can report it to Microsoft. For more information on how to report an issue, see [How to report a problem with the Visual C++ toolset or documentation](../overview/how-to-report-a-problem-with-the-visual-cpp-toolset.md).

0 commit comments

Comments
 (0)