Search Issue Tracker

Active

Under Consideration for 1.8.X

Votes

0

Found in [Package]

1.8.11

Issue ID

BUR-2593

Regression

No

Debugger breakpoint does not get hit when the breakpoint and the code are placed on a specific line

Package: Burst

-

Reproduction steps:
1. Open the attached "PROJECTFILE" project
2. Open the "Assets/SampleScene.unity" scene
3. Open the “Assets/Scripts/RotationSystem.cs” script with Visual Studio
4. Place a breakpoint on the line 31 of the code
5. Open the Attach to Process window from the Visual Studio Menu bar (Debug > Attach to Process)
6. Select the “Unity Editor” and click the “OK” button in the Attach to Process window
7. Enter the Play mode in the Unity Editor
8. Observe the Visual Studio and the Editor Game view

Expected result: The breakpoint gets hit and the GameObject in the Game view stops spinning
Actual result: The breakpoint does not get hit and the GameObject in the Game view continues to spin

Reproducible with: 1.8.11 (2022.3.17f1, 2023.2.4f1)
Couldn't test with versions: 2021.3.34f1, 2023.3.0b1 (Can not enter the Play mode due to Console errors)

Reproducible on: macOS Sonoma 14.2 (M1 Max), Windows 10
Not reproducible on: No other environment tested

Note:
-The breakpoint gets hit as expected when the line of code and the breakpoint are moved to the line 32
-Issue tested with Visual Studio 2022 for Mac and Visual Studio 2022
-The Visual Studio 2022 for Mac debugger may not attach to the Editor consistently on macOS Sonoma 14.2 (M1 Max)

Add comment

Log in to post comment