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
When debugging using the JLink debugger, it remains attached, and is able to (eventually) detect that the target has reset. However, if using defmt-print tcp to this target, it doesn't notice that the executable has changed, and will continue trying to decode messages from the old symbols. I'm not sure the best way to handle this, but just wanted to think about how it could be handled.
The text was updated successfully, but these errors were encountered:
When debugging using the JLink debugger, it remains attached, and is able to (eventually) detect that the target has reset. However, if using defmt-print tcp to this target, it doesn't notice that the executable has changed, and will continue trying to decode messages from the old symbols. I'm not sure the best way to handle this, but just wanted to think about how it could be handled.
The text was updated successfully, but these errors were encountered: