FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [April 2014 Threads] Get stack high water function gives the same valuesPosted by chaabanemalki on April 28, 2014 Hello,
Hello,
I tried to check the high water mark of my tasks.
When I use uxTaskGetStackHighWaterMark() inside task A (by passing NULL), I get task A high water mark. Works just fine. but when i try to check for the task A high water mark from task B I get the same value of high water mark as task B.
When I create task A, I made sure to define pxCreatedTask value and use it in task B to check the high water mark of Task A.
Not sure what I missed here !!
Thank you for your help
Get stack high water function gives the same valuesPosted by rtel on April 28, 2014 Could it be that both tasks genuinely have the same high water mark value?
You can easily step in to the uxTaskGetStackHighWaterMark() function in the debugger, then step over the call to prvGetTCBFromHandle() before inspecting the pxTCB variable to see the task being inspected by the function. The name of the task will be in pxTCB->pcTaskName.
Regards.
Get stack high water function gives the same valuesPosted by chaabanemalki on April 29, 2014 Thank you for the help.
I checked the pxTCB->pcTaskName and it has always the name of the current task rather than the task I wanted to check it's high water mark.
I passed the value of the pxCreatedTask rather than its adress. It is working correctly now
Thank you for your help
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|