- This topic has 10 replies, 3 voices, and was last updated 4 years, 6 months ago by
.
-
Posts
-
Hello, i have google-d a little and didn’t find answer, do you have similar functionality now?
Better FreeRTOS Debugging in Eclipse
I find heap and stack usage very helpful for fixing mem leaks. There is a table of all allocated memory locations and free areas
Also i have tested VisualGDB and did’t see task names in threads
Hi,
Thanks for the suggestion, we will consider adding detailed allocation analyzer to one of the next VisualGDB releases.
Currently VisualGDB supports FreeRTOS thread names through an open-source plugin (requires the custom edition or higher, should fully work in trial mode). If it doesn’t work, please share a diagnostic gdb log and a screenshot of the Threads window and we will investigate.
Although VisualGDB currently won’t show dynamically allocated regions, it can highlight the bounds of global variables and stack frames in the memory window. Simply use the advanced memory window and enable global variable highlighting via the toolbar.
Hi,
It is still on the roadmap, however it is hard to give any estimates currently, we are prioritizing a few other features over it, sorry.
Can you delivery for me VisualGDBExtensibility dependency ? I can continue this code on github and add Queue watch table.
Hi,
You can open the Threads view using the Debug->Windows->Threads command in Visual Studio
The VisualGDBExtensibility.dll library is shipped with VisualGDB (normally C:\Program Files (x86)\Sysprogs\VisualGDB\VisualGDBExtensibility.dll). Simply add it as a reference to the project referencing it and you should be able to build it.
Yes, please try VisualGDB 5.5 Preview 5: https://sysprogs.com/w/announcing-visualgdb-5-5-preview-5/
- You must be logged in to reply to this topic.