You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/debugger/TOC.md
+3-2Lines changed: 3 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -121,10 +121,11 @@
121
121
### [Error: Mixed-mode debugging for x64 processes is supported only when using Microsoft .NET Framework 4 or greater](error-mixed-mode-debugging-for-x64-processes-is-supported-only-when-using-microsoft-dotnet-framework-4-or-greater.md)
122
122
### [Error: Remote machine does not appear in a Remote Connections dialog](error-remote-machine-does-not-appear-in-a-remote-connections-dialog.md)
123
123
# [Debug Multithreaded Applications in Visual Studio](debug-multithreaded-applications-in-visual-studio.md)
124
-
## [Get Started Debugging Multithreaded Applications](how-to-use-the-threads-window.md)
124
+
## [Get Started Debugging Multithreaded Applications](get-started-debugging-multithreaded-apps.md)
125
125
## [Tools to Debug Threads and Processes](debug-threads-and-processes.md)
Copy file name to clipboardExpand all lines: docs/debugger/debug-multithreaded-applications-in-visual-studio.md
+27-21Lines changed: 27 additions & 21 deletions
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ In addition, multithreading introduces some new types of potential bugs. Often,
50
50
51
51
Visual Studio provides different tools for use in debugging multithreaded apps.
52
52
53
-
- For threads, the primary tools for debugging threads are the **Threads** window, thread markers in source windows, **Parallel Stacks** window, **Parallel Watch** window, and the **Debug Location** toolbar. To get started, see [Get started debugging a multithreaded application](../debugger/how-to-use-the-threads-window.md) and [Using the Parallel Stacks window](../debugger/using-the-parallel-stacks-window.md).
53
+
- For threads, the primary tools for debugging threads are the **Threads** window, thread markers in source windows, **Parallel Stacks** window, **Parallel Watch** window, and the **Debug Location** toolbar. To get started, see [Get started debugging a multithreaded application](../debugger/get-started-debugging-multithreaded-apps.md) and [Walkthrough: Debug using the Threads Window](../debugger/how-to-use-the-threads-window.md).
54
54
55
55
- For code that uses the [Task Parallel Library (TPL)](http://msdn.microsoft.com/Library/b8f99f43-9104-45fd-9bff-385a20488a23) or the [Concurrency Runtime](/cpp/parallel/concrt/concurrency-runtime/), the primary tools for debugging multithreaded applications are the **Parallel Stacks** window, the **Parallel Watch** window, and the **Tasks** window (the **Tasks** window also supports JavaScript). To get started, see [Walkthrough: Debugging a Parallel Application](../debugger/walkthrough-debugging-a-parallel-application.md) and [Walkthrough: Debugging a C++ AMP Application](http://msdn.microsoft.com/Library/40e92ecc-f6ba-411c-960c-b3047b854fb5).
56
56
@@ -60,16 +60,25 @@ Visual Studio provides different tools for use in debugging multithreaded apps.
60
60
61
61
Debugging a multithreaded application that has a user interface can be especially difficult. In that case, you might consider running the application on a second computer and using remote debugging. For information, see [Remote Debugging](../debugger/remote-debugging.md).
62
62
63
-
## In This Section
64
-
[Get started debugging a multithreaded application](../debugger/using-the-tasks-window.md).
65
-
A guided tour of thread debugging features, with emphasis on features in the **Threads** window [!INCLUDE[vs_orcas_long](../debugger/includes/vs_orcas_long_md.md)].
63
+
## In This Section
64
+
[Get started debugging a multithreaded application](../debugger/get-started-debugging-multithreaded-apps.md).
65
+
A guided tour of thread debugging features, with emphasis on features in the **Threads** window [!INCLUDE[vs_orcas_long](../debugger/includes/vs_orcas_long_md.md)].
66
66
67
-
[Debug Threads and Processes](../debugger/debug-threads-and-processes.md)
68
-
Explains the basics of debugging threads and processes.
67
+
[Tools for Debugging Threads and Processes](../debugger/debug-threads-and-processes.md)
68
+
Lists the features of the tools for debugging threads and processes.
[Walkthrough: Debug using the Threads Window](../debugger/how-to-use-the-threads-window.md).
74
+
A guided tour of thread debugging features, with emphasis on features in the **Threads** window [!INCLUDE[vs_orcas_long](../debugger/includes/vs_orcas_long_md.md)].
75
+
76
+
[Walkthrough: Debugging a Parallel Application](../debugger/walkthrough-debugging-a-parallel-application.md)
77
+
Walkthrough that shows how to use the Parallel Tasks and Parallel Stacks windows.
78
+
79
+
[How to: Use the Parallel Stack Window](../debugger/using-the-parallel-stacks-window.md)
80
+
Inspect values and expressions across multiple threads.
81
+
73
82
[How to: Use the Parallel Watch Window](../debugger/how-to-use-the-parallel-watch-window.md)
74
83
Inspect values and expressions across multiple threads.
75
84
@@ -80,28 +89,25 @@ Visual Studio provides different tools for use in debugging multithreaded apps.
80
89
Three ways to switch the debugging context to another thread.
81
90
82
91
[How to: Flag and Unflag Threads](../debugger/how-to-flag-and-unflag-threads.md)
83
-
Mark or flag threads that you want to give special attention to while debugging.
84
-
85
-
[How to: Set a Thread Name in Native Code](../debugger/how-to-set-a-thread-name-in-native-code.md)
86
-
Give your thread a name that you view in the **Threads** window.
87
-
88
-
[How to: Set a Thread Name in Managed Code](../debugger/how-to-set-a-thread-name-in-managed-code.md)
89
-
Give your thread a name that you view in the **Threads** window.
92
+
Mark or flag threads that you want to give special attention to while debugging.
90
93
91
94
[How to: Debug On a High-Performance Cluster](../debugger/how-to-debug-on-a-high-performance-cluster.md)
92
95
Techniques for debugging an application that runs on a high-performance cluster.
93
96
94
-
[Tips for Debugging Threads in Native Code](../debugger/tips-for-debugging-threads-in-native-code.md)
95
-
Simple techniques that can be useful for debugging native threads.
96
-
97
97
[Using the Tasks Window](../debugger/using-the-tasks-window.md)
98
-
Shows a list of all the managed or native task objects including their status and other useful info.
99
-
100
-
[Walkthrough: Debugging a Parallel Application](../debugger/walkthrough-debugging-a-parallel-application.md)
101
-
Walkthrough that shows how to use the Parallel Tasks and Parallel Stacks windows.
98
+
Shows a list of all the managed or native task objects including their status and other useful info.
102
99
103
100
[How to: Use the GPU Threads Window](../debugger/how-to-use-the-gpu-threads-window.md)
104
-
Examine and work with threads that are running on the GPU during debugging.
101
+
Examine and work with threads that are running on the GPU during debugging.
102
+
103
+
[Tips for Debugging Threads in Native Code](../debugger/tips-for-debugging-threads-in-native-code.md)
104
+
Simple techniques that can be useful for debugging native threads.
105
+
106
+
[How to: Set a Thread Name in Native Code](../debugger/how-to-set-a-thread-name-in-native-code.md)
107
+
Give your thread a name that you view in the **Threads** window.
108
+
109
+
[How to: Set a Thread Name in Managed Code](../debugger/how-to-set-a-thread-name-in-managed-code.md)
110
+
Give your thread a name that you view in the **Threads** window.
Copy file name to clipboardExpand all lines: docs/debugger/diagnostic-messages-in-the-output-window.md
+5-8Lines changed: 5 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,13 @@
1
1
---
2
-
title: "Diagnostic Messages in the Output Window | Microsoft Docs"
2
+
title: "Send Diagnostic Messages to the Output Window | Microsoft Docs"
3
3
ms.custom: ""
4
-
ms.date: "11/04/2016"
4
+
ms.date: "04/25/2017"
5
5
ms.reviewer: ""
6
6
ms.suite: ""
7
7
ms.technology:
8
8
- "vs-ide-debug"
9
9
ms.tgt_pltfrm: ""
10
10
ms.topic: "article"
11
-
f1_keywords:
12
-
- "vs.output"
13
11
dev_langs:
14
12
- "CSharp"
15
13
- "VB"
@@ -48,8 +46,8 @@ translation.priority.ht:
48
46
- "zh-cn"
49
47
- "zh-tw"
50
48
---
51
-
# Diagnostic Messages in the Output Window
52
-
You can write run-time messages to the Output window using the Debug class or the Trace class, which are part of the <xref:System.Diagnostics> class library. Use the Debug class if you only output in the Debug version of your program. Use the Trace class if you want output in both the Debug and Release versions.
49
+
# Send Diagnostic Messages to the Output Window
50
+
You can write run-time messages to the **Output** window using the `Debug` class or the `Trace` class, which are part of the <xref:System.Diagnostics> class library. Use the Debug class if you only output in the Debug version of your program. Use the Trace class if you want output in both the Debug and Release versions.
53
51
54
52
## Output Methods
55
53
The <xref:System.Diagnostics.Trace> and <xref:System.Diagnostics.Debug> classes provide the following output methods:
@@ -73,7 +71,6 @@ You can write run-time messages to the Output window using the Debug class or th
0 commit comments