Timer Double Abort Potential Issue within Car Node Example Project

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Urgent
    • SimpleLink Lowpower SDK F3 BLE5 Stack
    • BLE_LOKI-3768
    • BLE_LOKI_9_14_00_RC14
    • Hide
      BLE_LOKI_9_14_00
      BLE_LOKI_9_14_00_RC15
      Show
      BLE_LOKI_9_14_00 BLE_LOKI_9_14_00_RC15
    • CC27xx

      Description: Car Node procedure list timer is expired, and a callback is being called. Inside the callback we are calling to CarNode_clearTimeoutProcedures which can be called from multiple places in the code. This function clears the procedure list and checks if there is any timer currently running by checking a global variable, and if so - abort it. In this case the global variable still holds the timer handle (which was just expired), therefore we call to BLEAppUtil_abortTimer, which frees the timer DB inside it. Then, the function call stack gets back to bleapputil_localTimerCB which called the callback function and free the same timer DB once again

            Assignee:
            TI User
            Reporter:
            TI User
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Connection: Intermediate to External PROD System
                EXTSYNC-6082 - Timer Double Abort Potential Issue ...
                SYNCHRONIZED
                • Last Sync Date: