# At wits end - going to unhandled-IRQ handler from vTaskSwitchContext for no apparent reason **URL:** \ **Category:** Kernel\ **Created:** [April 30, 2021, 7:01pm UTC](https://forums.freertos.org/t/at-wits-end-going-to-unhandled-irq-handler-from-vtaskswitchcontext-for-no-apparent-reason/12473 "2021-04-30T19:01:49Z")\ **Posts on this page:** 1\ **Showing post:** 38
**Author:** ![RAc](https://d3iykfbgfh8zhg.cloudfront.net/user_avatar/forums.freertos.org/rac/32/1389_2.png) [@RAc](https://forums.freertos.org/u/RAc)\ **Post date:** [May 7, 2021, 6:44pm UTC](https://forums.freertos.org/t/at-wits-end-going-to-unhandled-irq-handler-from-vtaskswitchcontext-for-no-apparent-reason/12473/38 "2021-05-07T18:44:25Z")
> [@Cortex M4 hard fault finding root cause on LPC4078](https://forums.freertos.org/t/cortex-m4-hard-fault-finding-root-cause-on-lpc4078/11944/19): > > well, ok. Now we are talking taste though about which there is nothing to debate… I personally don’t like the idea of burning cycles for no other reason than gaining a little bit more error checking (even only in a debug scenario; if you activate this via #ifdef DEBUGVERSION, you gain differing runtime behavior which has its own problems). It potentially bloats the code significantly, sometimes very unintuitively - consider the code void SomeFn(unsigned long p\_Size) { unsigned char[p\_Size… --- _[View the full topic](https://forums.freertos.org/t/at-wits-end-going-to-unhandled-irq-handler-from-vtaskswitchcontext-for-no-apparent-reason/12473)._