Skip to content

Commit b65bc64

Browse files
Learn Build Service GitHub AppLearn Build Service GitHub App
authored andcommitted
Merging changes synced from https://github.com/MicrosoftDocs/visualstudio-docs-pr (branch live)
2 parents aec4c3d + 90e7475 commit b65bc64

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

docs/debugger/debug-with-copilot.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Debug with GitHub Copilot
33
description: Use Copilot to help debug your apps and provide performance insights.
4-
ms.date: 9/3/2025
4+
ms.date: 9/12/2025
55
ms.update-cycle: 180-days
66
ms.topic: how-to
77
dev_langs:
@@ -55,6 +55,7 @@ In addition, Copilot provides more precise help for some targeted scenarios, suc
5555
|IEnumerable tabular visualizer|See [Get AI assistance](../debugger/view-data-in-tabular-visualizer.md#get-ai-assistance).|
5656
|Inline return values|See [View return values of method calls](../debugger/autos-and-locals-windows.md#view-inline-return-values-of-method-calls-in-the-code-editor).|
5757
|Multithreaded debugging|See [Get AI assistance with Threads view](../debugger/using-the-parallel-stacks-window.md#get-ai-assistance).|
58+
|Troubleshooting breakpoints|Select the **Ask Copilot** button if you get a source code mismatch associated with the message **This breakpoint will not currently be hit.**|
5859

5960
In most of these scenarios, you get targeted assistance by using the **Ask Copilot** ![Screenshot of Ask Copilot button.](../debugger/media/vs-2022/debug-with-copilot-ask-copilot-button.png) or **Analyze with Copilot** button. Copilot already knows the context for your questions. For example, it knows the current call stack, the code line you're asking about, and the name of the exception (if one occurred), so you don't need to provide context yourself in chat. Copilot also provides suggestions for the use of conditional breakpoints and tracepoints.
6061

0 commit comments

Comments
 (0)