JUCE Message Thread (1): signal SIGABRT - how to deal with that?

I’ve heard some strange things about SIGABRT. But don’t understand it at all.
Could anyone help me how to deal with that?

Those usually pop up due to memory corruption, heap overflow, or double-freeing. It’s an error being thrown by the standard library upon an internal error.

Use a tool like Valgrind or be smart about your memory allocation (IE don’t do it manually, use RAII principles/practices).

1 Like

Thanks I will try to read something about what you propose. Now it’s totally new for me.