Allow printing defmt output to the RTT console

[xoviat]

defmt is widely used as a logger in the rust embedded ecosystem. This allows seamlessly debugging a rust program while printing defmt output at the same time.

[xoviat]

Oh, and defmt-print must be installed for this to work. Maybe add a tooltip for that?

[xoviat]

@haneefdm Do you have questions about this?

[haneefdm]

Thank you for the PR and I agree it will be very useful for Rust developers Before I look at it, I have a request. I need an example project available on github for me to begin looking at it.

It will be my test case as well. Your github example project should be ready to run with minimal effort on my part (preferably on a Mac). I cannot accept what I cannot test. I am not Rust-educated either.

I you can also update the source code to add a reference to the example github then that would be nice.

Sorry, it took me a long time to get to it. Personal health reasons.

[haneefdm]

I lied. I did a cursory review. I don't know what is going on with the executable in the RTTConfigureEvent.

And, then in the constructor of the DefmtSocketRTTSource, you are trying to re-resolve the executable. How can we be assured that the debugger and the RTT decoder is looking at the same executable? Do you need help from the debugger?

Also, I think that the executable property in launch.json is optional if you have the symbolFiles property.

[xoviat]

I'll get back to this in a few days. I need to refresh my memory after taking care of some other stuff.

[HaoboGu]

Any updates? I got the same problem, cortex-debug cannot print defmt's RTT log

[hazer-hazer]

Installed extension from this PR, everything works perfectly, except vscode does not hint to set defmt as type option in rttConfig.decoders. @Marus Any chance to see this changes in master? 💌

[haneefdm]

@xoviat I am still waiting for the PRs original author.