Describing C as having no safety protections, as the table does, is wrong. There are plenty of tools in the C toolchain to address most of the issues listed. Null pointer dereferences can be caught by your OS/arch with a segfault. The classes of memory corruption errors described can be caught with sanitizers and valgrind. If you want a stack trace, you can run your program under gdb with debug symbols.
Describing C as having no safety protections, as the table does, is wrong. There are plenty of tools in the C toolchain to address most of the issues listed. Null pointer dereferences can be caught by your OS/arch with a segfault. The classes of memory corruption errors described can be caught with sanitizers and valgrind. If you want a stack trace, you can run your program under gdb with debug symbols.