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] [March 2008 Threads] deleting twice crashes the applicationPosted by mkrug on March 1, 2008 Hello,
in my application serveral tasks could delete one task (say: taks_to_delete). Additionally I have quite a high interrupt load that starts (unblock) most of my tasks. So the following could happen 1.) a tasks issues the command vTaskDelete(task_to_delete_handle) 2.) before the command gets completed a interrupt occurs that will unblock a high priority task 3.) this task also issues the command vTaskDelete(task_to_delete_handle)
In that cases it seems to me that my application crashes. I assume it happens when vTaskDelete() call try's to delete a task that is not existing anymore. So far I had no idea how to verify my assumption. So here are my questions: a) Is there a possibility to 'survive' a vTaskDelete() call that try's to delete a tasks that is not existing anymore ? b) is there a possibility to check which RTOS API-call causes the system crash ?
Best Regards Markus
RE: deleting twice crashes the applicationPosted by Adrian Carpenter on March 1, 2008 If you're using an ARM processor and "by crash" you've ended up in an abort handler, then r14 gives the address that caused the abort. You can then work back (using your map file) to what caused the abort.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|