Valgrind fails when ReallocSizeZero error is thrown

When running a program that has a realloc() call of size 0, the following error is reported: Memcheck: Error occurred parsing Valgrind output: Unknown memcheck error kind "ReallocSizeZero"

After this error, parsing of output ceases and all Valgrind output goes to the output console, and can quickly exceed the output buffer.

I encountered this within the NVIDIA OpenGL and Vulkan libraries, meaning that trying to track a memory error in a graphical application is guaranteed to trigger it on some systems.