Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
0
Found in
2018.4
2019.2
2019.3
2020.1
Issue ID
1215119
Regression
No
No debug information for NativeArray<T> objects available when debugging IL2CPP builds
Steps to reproduce:
1. Open the attached project (case_1215119.zip)
2. Build the project as Standalone with Scripting Backend set to IL2CPP and "Development Build", "Script Debugging" and "Wait for Managed Debugger" checked
3. Open Script.cs and put a breakpoint on line 19
4. Run the executable
5. In Visual Studio, attach a Managed Debugger (Debug -> Attach Unity Debugger)
6. Click OK in the popup box for debugging to continue
7. Wait for the breakpoint to be hit
8. Mouse over the "array" variable in Visual Studio
Expected result: NativeArray<T> objects can be inspected (length and other property information available)
Actual result: NativeArray<T> objects cannot be inspected - not even a popup box is given
Reproduced in: 2018.4.17f1, 2019.2.20f1, 2019.3.1f1, 2020.1.0a22
Cannot test with: 2017.4.36f1 (No IL2CPP)
Note:
- The bug is only present in IL2CPP builds - Mono builds do not reproduce the issue
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a3
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b8:
Allow inspection of NativeArray objects in the debugger
Resolution Note (fix version 2019.3):
Fixed in 2019.3.13f1