Thread information while debugging Matter samples

[JulNeu2332]

Hallo, 

I am currently trying to debug the Matter samples on the NRF5340 DK. They all work fine, but I have a problem with the "Thread Viewer" in VS Code while debugging on target.

With other non-Matter Zephyr samples I had no issue opening the "Thread viewer" to see all Threads with their names, priorities, sates etc. 

Whenever I try to debug a Matter sample it only shows Thread with some id number, which is not helpful. I want to know the names, priorities of the Threads used in the Matter samples.

Thanks for your attention. I’m looking forward to a reply.

 Julius

[Susheel Nuguru]

I am not so familiar compiling thread applications but should there be Kconfig options for setting the optimization levels to debug for the app which help debuggers like this to have better information about threads?

[JulNeu2332]

All Kconfig options for Debugging and optimization levels are the same in these samples. 

However I found a solution to my Problem. 

With the Ozone Debugger I can use the Zephyr Plugin with > Project.SetOSPlugin("ZephyrPlugin.js"). Then I open the Zephyr window to see the running Threads with all their Information.

I still dont know why it wouldn't work with the VS Code gdb Debugger, I did not change any of the Kconfig options. 

[Susheel Nuguru]

Thanks for coming back with the workaround, I can pass this information to the VisualStudio Code team about the possible handling of Thread information in the VSC gdb window without the ozone plugin

[Susheel Nuguru]

The team have now acknowledged and created for this. Hopefully we will have the the object offsets used to determine symbol offsets in the the thread plugin.

reference for the internal ticket. VSC-1286 and VSC-1287