Updated VM & VS 2 days ago.

I have a problem with a feature/s of the debugger causing my code to crash, and a subsequent restart. ( more further below)
Whilst researching the cause of this, I used the "blink" code  with a few added variables, for proving the debugger. 

I noted the following :- Expression window.
1)  The documentation shows red text & a yellow cell in the expression window.  In reality these colours are not present. A bit confusing to a new start with a Very Old Brain. I appreciate maintenance of a project like VM is difficult.

2)The code pauses if the appropriate box is unticked and proceeds as expected when the appropriate key is pressed. Trace configuration window.

3) When appending the variable name with =? it is possible to change the value in the variable, whilst the code is Running.  Just select the approppriate cell, change the value and then hit Enter.

Re my real problem - 
My code runs Ok with and without debug.
If however I try to use =? or @Report.. functions, it crashes.
Work in progress - any suggestions welcome.

Attached is the build file for the code that crashes when I apply the  =? or @Report...  functions.

Apologies for not including the build file earlier, I have just found how to save & retrieve it.

Other requuested data to follow.........

Thanks for the project and the logs.

Do you see the same crash when using the editable variable, but with the breakpoint not set to continue code execution?

I can't currently replicate the crash with this sketch, could you try running a repair on VS2022?

Also can you attach the Micro Build output for the simple project so I can ensure I am using all the same settings (in case they differ from your main project).

Thanks for the update, I don't think the repair is needed as the Uno works.

We will look into any specific Mega Code for the Debugger and update when we have a fix or workaround available.

Many thanks.
Just tried Mega with a breakpoint and a {variable} -it crashed.
Removed breakpoint;  it runs & displays variable.

Good evening,
Re my last post - this test was with my project file.

The blink file runs on the mega, debug, {variable=?}, @Report, breakpoint,- all no problem.

My project file fails on the Mega wihen I use {variable=?}, @Report, breakpoint.

You have the build file for the crashing configuration. I sent it at 11:43 - its there I have just opened it  its called DSG5Build.txt

With the Uno - there are no problems.

Thanks for the clarification.

The log for the crashing configuration looks to be a much larger/complex project than the blink sketch which was sent over.

I assume the blink sketch on the mega fails with the single breakpoint with just the {f=?} action set? (without any @Report or other features enabled)

Thanks for clarifying, and explains why I cannot repro this on the Mega with the blink sketch etc...

When you said your code crashes on the Mega, is it that the board needs to be reset to get it running again?

Is it only when you change the variable in the Serial Debugger that it all goes wrong?

Finally, does your code use the same Serial port that the Debugger is using? (I only ask as the serial debugger can be moved onto a different Serial port if needed so the comm's for the debugger and your code become completely isolated)

Thanks for the update.

Would it be possible to ZIP the whole solution (minus the .vs folder) and email it to us with a link to this thread to investigate?

We will of course remove the files once the issue is resolved.

Thanks for the files.

Running this with just the boards (no LCD Screen etc) we see the same problem with your code crashing and restarting on the mega.

If you change the printf statement on line 324 to be separate Serial.print statements then it all seems to work as expected with the debugger enabled, and you see this output in the Serial Monitor (when using printf you don't).

This is likely down to how Stdout is interpreted by the microcontroller, the Uno only has "Serial" wheras the Mega has Serial, Serial1, Serial2, Serial3.

I'm not currently sure why the Serial Debugger causes the crash when using the editable variable, however this does add code which attempts to read and write to the serial buffer.  We will try and debug this to get a better understanding of what is happening here.