Skip to content

Commit 3057a90

Browse files
gewarrengewarren
committed
table fix ups
1 parent e168758 commit 3057a90

16 files changed

+106
-106
lines changed

‎docs/debugger/c-cpp-assertions.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -103,10 +103,10 @@ VERIFY ( myFnctn(0)==1 ) // safe
103103
The CRTDBG.H header file defines the [_ASSERT and _ASSERTE macros](/cpp/c-runtime-library/reference/assert-asserte-assert-expr-macros) for assertion checking.
104104

105105

106-
| Macro | Result |
107-
|------------|-------------------------------------------------------------------------------------------------|
108-
| `_ASSERT` | If the specified expression evaluates to FALSE, the file name and line number of the `_ASSERT`. |
109-
| `_ASSERTE` | Same as `_ASSERT`, plus a string representation of the expression that was asserted. |
106+
| Macro | Result |
107+
|------------| - |
108+
| `_ASSERT` | If the specified expression evaluates to FALSE, the file name and line number of the `_ASSERT`. |
109+
| `_ASSERTE` | Same as `_ASSERT`, plus a string representation of the expression that was asserted. |
110110

111111
`_ASSERTE` is more powerful because it reports the asserted expression that turned out to be FALSE. This may be enough to identify the problem without referring to the source code. However, the Debug version of your application will contain a string constant for each expression asserted using `_ASSERTE`. If you use many `_ASSERTE` macros, these string expressions take up a significant amount of memory. If that proves to be a problem, use `_ASSERT` to save memory.
112112

‎docs/debugger/debugger-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,9 +19,9 @@ ms.workload:
1919

2020
The Visual Studio debugger allows you to observe the run-time behavior of your program and locate logic errors. The debugger works with all Visual Studio programming languages and their associated libraries. With the debugger, you can break execution to step through your code and evaluate variables in your application.
2121

22-
| | |
22+
| | |
2323
|---------|---------|
24-
| ![movie camera icon for video](../install/media/video-icon.png "Watch a video") | [Watch a video](https://mva.microsoft.com/en-US/training-courses-embed/getting-started-with-visual-studio-2017-17798/Debugger-Feature-tour-of-Visual-studio-2017-sqwiwLD6D_1111787171) on debugging that shows similar steps. |
24+
| ![movie camera icon for video](../install/media/video-icon.png "Watch a video") | [Watch a video](https://mva.microsoft.com/en-US/training-courses-embed/getting-started-with-visual-studio-2017-17798/Debugger-Feature-tour-of-Visual-studio-2017-sqwiwLD6D_1111787171) on debugging that shows similar steps. |
2525

2626
The debugger allows you to set breakpoints, inspect variables and set watches, view the call stack, debug on remote devices, debug multithreaded apps, and leverage many other features.
2727

‎docs/debugger/debugging-wpf.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,9 +24,9 @@ ms.workload:
2424

2525
## Related Topics
2626

27-
| Title | Description |
28-
|----------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
29-
| [How to: Use the WPF Tree Visualizer](../debugger/how-to-use-the-wpf-tree-visualizer.md) | You can use the WPF Tree Visualizer to explore the visual tree of a WPF object and view the WPF dependency properties for the objects in that tree. This topic describes the user interface of the WPF Tree Visualizer. |
27+
| Title | Description |
28+
| - | - |
29+
| [How to: Use the WPF Tree Visualizer](../debugger/how-to-use-the-wpf-tree-visualizer.md) | You can use the WPF Tree Visualizer to explore the visual tree of a WPF object and view the WPF dependency properties for the objects in that tree. This topic describes the user interface of the WPF Tree Visualizer. |
3030
| [How to: Display WPF Trace Information](../debugger/how-to-display-wpf-trace-information.md) | [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] can receive debug trace information from WPF applications and display that information in the **Output** window. This topic describes how to enable and customize the display of WPF trace information. |
3131

3232
## See Also

‎docs/debugger/get-started-debugging-multithreaded-apps.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,9 +23,9 @@ ms.workload:
2323
# Get started debugging multithreaded applications in Visual Studio
2424
Visual Studio provides several tools and user interface elements to help you debug multithreaded applications. This tutorial shows how to use thread markers, the **Parallel Stacks** window, the **Parallel Watch** window, conditional breakpoints, and filter breakpoints . This tutorial takes only a few minutes, but completing it will familiarize you with the features for debugging multithreaded applications.
2525

26-
| | |
26+
| | |
2727
|---------|---------|
28-
| ![movie camera icon for video](../install/media/video-icon.png "Watch a video") | [Watch a video](https://mva.microsoft.com/en-US/training-courses-embed/getting-started-with-visual-studio-2017-17798/Debugging-Multi-threaded-Apps-in-Visual-Studio-2017-MoZPKMD6D_111787171) on multithreaded debugging that shows similar steps. |
28+
| ![movie camera icon for video](../install/media/video-icon.png "Watch a video") | [Watch a video](https://mva.microsoft.com/en-US/training-courses-embed/getting-started-with-visual-studio-2017-17798/Debugging-Multi-threaded-Apps-in-Visual-Studio-2017-MoZPKMD6D_111787171) on multithreaded debugging that shows similar steps. |
2929

3030
Other topics provide additional information on using other multithreaded debugging tools:
3131

‎docs/debugger/getting-started-with-the-debugger.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,9 +21,9 @@ ms.workload:
2121

2222
This article introduces the features of the Visual Studio debugger in a step-by-step walkthrough. If you want a higher-level view of the debugger features, see [Debugger Feature Tour](../debugger/debugger-feature-tour.md). When you *debug your app*, it usually means that you are running your application with the debugger attached. When you do this, the debugger provides many ways to see what your code is doing while it runs. You can step through your code and look at the values stored in variables, you can set watches on variables to see when values change, you can examine the execution path of your code, see whether a branch of code is running, and so on. If this is the first time that you've tried to debug code, you may want to read [Debugging for absolute beginners](../debugger/debugging-absolute-beginners.md) before going through this article.
2323

24-
| | |
24+
| | |
2525
|---------|---------|
26-
| ![movie camera icon for video](../install/media/video-icon.png "Watch a video") | [Watch a video](https://mva.microsoft.com/en-US/training-courses-embed/getting-started-with-visual-studio-2017-17798/Debugger-Feature-tour-of-Visual-studio-2017-sqwiwLD6D_1111787171) on debugging that shows similar steps. |
26+
| ![movie camera icon for video](../install/media/video-icon.png "Watch a video") | [Watch a video](https://mva.microsoft.com/en-US/training-courses-embed/getting-started-with-visual-studio-2017-17798/Debugger-Feature-tour-of-Visual-studio-2017-sqwiwLD6D_1111787171) on debugging that shows similar steps. |
2727

2828
Although the demo app is C# and C++, the features are applicable to Visual Basic, JavaScript, and other languages supported by Visual Studio (except where noted). The screenshots are in C#.
2929

‎docs/debugger/graphics/graphics-event-list.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ Use the Graphics Event List in Visual Studio Graphics Analyzer to explore the Di
7777
To create groups and markers in Direct3D 12, use the APIs described in this section. The table below summarizes the APIs that you can use depending on whether you are marking events in a command queue or command list.
7878

7979
|API Description|[ID3D12CommandQueue](/windows/desktop/api/d3d12/nn-d3d12-id3d12commandqueue)|[ID3D12GraphicsCommandList](/windows/desktop/api/d3d12/nn-d3d12-id3d12graphicscommandlist)|
80-
|---------------------|----------------------------------------------------------------------------|-----------------------------------------------------------------------------------|
80+
|---------------------| - | - |
8181
|Check user-defined event availability|[PIXGetStatus](https://msdn.microsoft.com/library/f7ebd985-fb5d-46d7-abec-099df4b9be0e)|[PIXGetStatus](http://msdn.microsoft.com/en-us/1046ac43-a0a3-42bf-bae8-14aa72fa7567)|
8282
|Begin an event group|[PIXBeginEvent](http://msdn.microsoft.com/en-us/5f51fff7-f313-4558-965b-2a443653cd7b)|[PIXBeginEvent](http://msdn.microsoft.com/en-us/4ddb3311-b9b5-449a-bbfb-7634e0d56e87)|
8383
|End an event group|[PIXEndEvent](http://msdn.microsoft.com/en-us/fb526bf2-c17d-4a2a-8665-3b577a0f7fba)|[PIXEndEvent](http://msdn.microsoft.com/en-us/a3cd34a9-9dd9-40e1-ae86-0214b25ff185)|
@@ -87,7 +87,7 @@ Use the Graphics Event List in Visual Studio Graphics Analyzer to explore the Di
8787
To create groups and markers in Direct3D 11 or earlier, use the APIs described in this section. The table below summarizes the APIs that you can use for different versions of Direct3D 11 and earlier versions of Direct3D.
8888

8989
|API Description|[ID3D11DeviceContext2](/windows/desktop/api/d3d11_2/nn-d3d11_2-id3d11devicecontext2) (Direct3D 11.2)|[ID3DUserDefinedAnnotation](http://go.microsoft.com/fwlink/p/?LinkID=250967) (Direct3D 11.1)|D3DPerf_ API family (Direct3D 11.0 and earlier)|
90-
|---------------------|---------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|--------------------------------------------------------|
90+
|---------------------| - | - | - |
9191
|Begin an event group|`BeginEventInt`|`BeginEvent`|`D3DPerf_BeginEvent`|
9292
|End an event group|`EndEventInt`|`EndEvent`|`D3DPerf_EndEvent`|
9393
|Create an event marker|`SetMarkerInt`|`SetMarker`|`D3DPerf_SetMarker`|
@@ -104,10 +104,10 @@ Visual Studio 2017 and greater contain the **Resource History** window. Selecti
104104
This window allows you to view the history of the selected item in the event list. The dropdown at the top can be used to select other items to view the history of. The top half of the window contains the **Frame Setup Events**. These are the events which fall into the *Create* type category and are calls that typically initialize and create the resource. The bottom half of the window contains the **Frame Events** section. These are the normal read and write events that occur during the usage of the resource.
105105

106106

107-
| Column | Description |
108-
|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
109-
| **Type** | Shows the type of the entry, typically *Create*, *Read* and *Write*. |
110-
| **View** | Shows a thumbnail of the resource at that moment in time. Double-click the thumbnail to open a details view of the resource at that time. |
107+
| Column | Description |
108+
|-----------| - |
109+
| **Type** | Shows the type of the entry, typically *Create*, *Read* and *Write*. |
110+
| **View** | Shows a thumbnail of the resource at that moment in time. Double-click the thumbnail to open a details view of the resource at that time. |
111111
| **Event** | Shows the method call that occurred which generated the event. Any additional history on individual items can be viewed by selecting the watch icon ![watch icon](media/gfx_watch.png) on the appropriate line. Also, any item which is drawn in blue text, such as `m_commandList` in the screenshot above, can be selected for more details. |
112112

113113
<!-- /VERSIONLESS -->

‎docs/debugger/graphics/graphics-frame-validation.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -22,13 +22,13 @@ Visual Studio 2017 and greater support the **Frame Validation** tool. The Frame
2222
Click the **Run Validation** button at the top left corner to initiate the analysis. It may take several minutes to complete depending on the complexity of the frame. The data which appears here is a combination from two sources: the messages that D3D itself emits when [SDK Layers](/windows/desktop/direct3d11/overviews-direct3d-11-devices-layers) is enabled, and data that is collected from the tool's own internal state tracking. Once complete, you will see several columns of data:
2323

2424

25-
| **Column** | **Description** |
26-
|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
27-
| Event Id | ID which maps to an entry in the [Event List](graphics-event-list.md) window. |
28-
| Severity | Corruption, Error, Warning, Info, or Message. |
29-
| Category | Application Defined, Miscellaneous, Initialization, Cleanup, Compilation, State Creation, State Setting, State Getting, Execution, Resource Manipulation, Shader, Redundant, and Unused. |
30-
| Message | The message associated with the event. |
31-
| Event | The event associated with the error or warning. |
25+
| **Column** | **Description** |
26+
|------------| - |
27+
| Event Id | ID which maps to an entry in the [Event List](graphics-event-list.md) window. |
28+
| Severity | Corruption, Error, Warning, Info, or Message. |
29+
| Category | Application Defined, Miscellaneous, Initialization, Cleanup, Compilation, State Creation, State Setting, State Getting, Execution, Resource Manipulation, Shader, Redundant, and Unused. |
30+
| Message | The message associated with the event. |
31+
| Event | The event associated with the error or warning. |
3232

3333
## See Also
3434
[Graphics Diagnostics (Debugging DirectX Graphics)](visual-studio-graphics-diagnostics.md)

‎docs/debugger/graphics/graphics-log-document.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -102,11 +102,11 @@ The Graphics Log document is the record of graphics events that occurred while y
102102
Lists information about the graphics log document.
103103

104104

105-
| Property | Description |
106-
|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
107-
| **Created by** | The name of the app that created the graphics log document. For example, if the capture session was initiated from [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] (manual capture) the value of this property is [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)]. |
108-
| **Session Start Time** | The date and time that the capture session began. |
109-
| **Size** | The size of the graphics log document. |
105+
| Property | Description |
106+
|------------------------| - |
107+
| **Created by** | The name of the app that created the graphics log document. For example, if the capture session was initiated from [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] (manual capture) the value of this property is [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)]. |
108+
| **Session Start Time** | The date and time that the capture session began. |
109+
| **Size** | The size of the graphics log document. |
110110

111111
## See Also
112112
[Walkthrough: Missing Objects Due to Vertex Shading](walkthrough-missing-objects-due-to-vertex-shading.md)

‎docs/debugger/graphics/reference-programmatic-capture.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,8 +32,8 @@ Graphics Diagnostics supports programmatic control over its capture features, th
3232

3333
## Related Articles
3434

35-
| Title | Description |
36-
|---------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
35+
| Title | Description |
36+
| - | - |
3737
| [Capturing Graphics Information](capturing-graphics-information.md) | Shows how to capture graphics information from your DirectX-based app so that you can use [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] Graphics Diagnostics tools to diagnose rendering problems. |
38-
| [Overview](overview-of-visual-studio-graphics-diagnostics.md) | Shows how Graphics Diagnostics can help you debug rendering errors in DirectX games and apps. |
38+
| [Overview](overview-of-visual-studio-graphics-diagnostics.md) | Shows how Graphics Diagnostics can help you debug rendering errors in DirectX games and apps. |
3939

0 commit comments

Comments
 (0)