• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 22 subscribers
  • Views 978 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

os_tsk_delete

Stephen Isidore

hi,

I have some scheduling problems with my application when I 'm deleting task with the fucntion os_tsk_delete in ARTX

My application freeze and when I'm inspecting state of task with µVision3, I can see two thing :
- Sometimes the priority of the task had changed. it is not the priority that i have given when in create the task with os_create_task functions so my application don't running correctly
- The other result is that only scheduler task (highest priority) is running as my TCB's structure has been damaged.

Can I delete a running task ?

What's happened when you delete a task A which had created task B and C ?

thanks for yor help

Parents
  • 0 in reply to Stephen Isidore

    Yes, If task A "owns" a mutex and then task A is deleted, no other task will be able to aquire the mutex and A will still own it (even thoght there is no longer any A).

    That is how it behaves.

    Any memory allocated by a task and not freed before a delete will still be allocated with no way to know how to free it.

    Any Mutxes owned by a task before a delete will still be "owned" with no way to know how to release it.

Reply
  • 0 in reply to Stephen Isidore

    Yes, If task A "owns" a mutex and then task A is deleted, no other task will be able to aquire the mutex and A will still own it (even thoght there is no longer any A).

    That is how it behaves.

    Any memory allocated by a task and not freed before a delete will still be allocated with no way to know how to free it.

    Any Mutxes owned by a task before a delete will still be "owned" with no way to know how to release it.

Children
No data