Identify current task after a crash

jakbird wrote on Thursday, October 04, 2007:

Is there a specific global inside the RTOS where a crash handler for ARM aborts can identify which task was active when the exception occurred?  Since this is a crash situation I don;t want to make any RTOS calls.  The specific situation I’m trying to trace is where code jumps to non-existent memory, causing an ARM prefetch abort.  The link address for the exception only tells me the bad address, not where the real error is located.
  Jack Peacock

sotd wrote on Thursday, October 04, 2007:

Look at pxCurrentTCB in your debugger.  This will tell you the task that is currently running.