Skip to content

Commit e8da3d3

Browse files
authored
Merge pull request #9726 from haywoodsloan/7473-copilot-breakpoints
AB#7473 - Add Copilot information to article on troubleshooting breakpoints
2 parents 3284ff4 + 68c47a5 commit e8da3d3

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

support/developer/visualstudio/debuggers/troubleshooting-breakpoints.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Troubleshoot breakpoints in the debugger
33
description: If a breakpoint is disabled or couldn't be set, it's displayed as a hollow circle. Look here information on problems that can occur when setting breakpoints.
4-
ms.date: 06/27/2024
4+
ms.date: 09/12/2025
55
author: aartig13
66
ms.author: aartigoyle
77
ms.reviewer: mikejo
@@ -44,6 +44,8 @@ Navigate to **Debug** > **Windows** > **Modules** when debugging and check wheth
4444

4545
### "… the current source code is different from the version built into..."
4646

47+
Alternatively, the message might say **"… the source code is different from the original version."**.
48+
4749
If a source file has changed and the source no longer matches the code you're debugging, the debugger won't set breakpoints in the code by default. Normally, this problem happens when a source file is changed, but the source code wasn't rebuilt. To fix this issue, rebuild the project. If the build system thinks the project is already up-to-date even though it isn't, you can force the project system to rebuild. Rebuild the project either by saving the source file again or by cleaning the build output before building.
4850

4951
In rare scenarios, you may want to debug without having matching source code. Debugging without matching source code can lead to a confusing debugging experience, so make sure how you want to continue.
@@ -53,6 +55,10 @@ Follow one of the options to disable these safety checks:
5355
- To modify a single breakpoint, hover over the breakpoint icon in the editor and select the settings (gear) icon. A peek window is added to the editor. At the top of the peek window, there's a hyperlink that indicates the location of the breakpoint. Select the hyperlink to allow modification of the breakpoint location and check **Allow the source code to be different from the original**.
5456
- To modify this setting for all breakpoints, go to **Debug** > **Options and Settings**. On the **Debugging/General** page, clear the **Require source files that exactly match the original version** option. Make sure to reenable this option when you're finished debugging.
5557

58+
#### Get AI assistance
59+
60+
If you have [Copilot](/visualstudio/ide/visual-studio-github-copilot-extension), you can use AI assistance to help resolve source code mismatch issues. Copilot performs a lightweight validation of the code and enables a relaunch of the debugger if it successfully identifies a cause. Use the **Ask Copilot** button at the end of the error message.
61+
5662
## The breakpoint was successfully set (no warning), but didn't hit
5763

5864
This section provides information to troubleshoot issues when the debugger isn't displaying any warnings – the breakpoint is a solid red circle while actively debugging, yet the breakpoint isn't being hit.

0 commit comments

Comments
 (0)