operator new and interrupts

andreas von kaenel

Hi all,

I have a project coded in C++, combined with some timecritical interrupts. In the background loop I create a singleton object at runtime, so interrupts are enabled at this time. Unfortunately this leads into an illegal op trap in the "new" method. If I create the singleton object before enabling the interrupts, things are fine. Although I can life with this workaround I would like to understand what I am doing wrong. Can anybody guide me?

BR Andreas

over 14 years ago

0 Archaeologist over 14 years ago

TI__Guru* 84285 points

It's not safe to call most RTS functions in interrupts, and heap allocation is one class of such functions. If an interrupt occurs in the middle of a heap allocation or de-allocation, the heap will be corrupted, leading to all sorts of strange errors. Avoid calling interrupt- or thread-unsafe functions during an interrupt. Even if the heap allocation functions were made to be thread-safe, they might never be truly interrupt-safe.

0 andreas von kaenel over 14 years ago in reply to Archaeologist

Genius 4925 points

That's a statement, thank you for the reply

BR Andreas

Code Composer Studio™︎

Code Composer Studio forum

operator new and interrupts