Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show FreeRTOS Queues #41

Open
srobertjames opened this issue Sep 29, 2023 · 3 comments · May be fixed by #45
Open

Show FreeRTOS Queues #41

srobertjames opened this issue Sep 29, 2023 · 3 comments · May be fixed by #45
Labels
enhancement New feature or request

Comments

@srobertjames
Copy link

Is your feature request related to a problem? Please describe.
When debugging a FreeRTOS project, I need to know the contents of a FreeRTOS Queue

Describe the solution you'd like
Similar to vscode watches: A table or tree showing FreeRTOS Queues, their size, and their contents (as an array)

Describe alternatives you've considered

  1. Looking at the u member in the watches, and then looking at the memory view
  2. Other debuggers seem to support this
@srobertjames
Copy link
Author

Are you able to respond to this?

@PhilippHaefele
Copy link
Collaborator

@srobertjames Sorry that nobody responded yet. @haneefdm did the general and FreeRTOS implementation, but our free time is somehow limited.

Maybe someone else (e.g. also me) can help when there's spare time for this.

We're also happy to receive PullRequests.

So most likely for now this means that this feature will not be implemented very soon.

@PhilippHaefele PhilippHaefele added the enhancement New feature or request label Jan 7, 2024
@haneefdm
Copy link
Contributor

haneefdm commented Jan 7, 2024

I will take a look in a couple of weeks. Had been very busy lately.

@hwmland hwmland linked a pull request Jan 13, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants