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
set breakpoint, for example at line "Thread.Sleep(5000);", wait until it stops there
nothing bad should happen - remove breakpoint and press continue
let run for some time (15 s or so)
enable "Autos" window (Debug->Windows->Autos)
set same breakpoint as before, let it run into it
remove breakpoint and press continue
now, a "System.NullReferenceException" should happen in DateTime.cs
Other suggested things
Expected behaviour
No exception should be thrown.
Screenshot
Additional context
Make an effort to fix the bug
Our fix for the moment is to keep the "Autos" window closed. If I would have to guess about the cause of the issue, I would say it's because the debugger wants to generate a string representation for the debug output.
The text was updated successfully, but these errors were encountered:
Details about Problem
nanoFramework area: ( Visual Studio extension )
VS version: 15.9.22
VS extension version: 2017.1.8.16
Target: STM32F769I_DISCOVERY
Firmware image version:
Device capabilities output:
device_cap.txt
Assemblies:
CoreLibrary: v1.7.2-preview.5
Runtime.Native: v1.2.0-preview.15
Description
Visual Studio "Autos" window causes System.NullReferenceException in mscorlib.
Detailed repro steps so we can see the same problem
make sure the target has the newest firmware (
ST_STM32F769I_DISCOVERY-1.4.0-preview.181.zip
), and the VS project has the abovementioned assemblies referenced.
open RTC test program:
test_program.zip
start debugging session
make sure "Autos" window is closed
set breakpoint, for example at line "Thread.Sleep(5000);", wait until it stops there
nothing bad should happen - remove breakpoint and press continue
let run for some time (15 s or so)
enable "Autos" window (Debug->Windows->Autos)
set same breakpoint as before, let it run into it
remove breakpoint and press continue
now, a "System.NullReferenceException" should happen in DateTime.cs
Other suggested things
Expected behaviour
No exception should be thrown.
Screenshot
Additional context
Make an effort to fix the bug
Our fix for the moment is to keep the "Autos" window closed. If I would have to guess about the cause of the issue, I would say it's because the debugger wants to generate a string representation for the debug output.
The text was updated successfully, but these errors were encountered: