What does it mean for a binary to be 'munched' after it is compiled?

Question

The title pretty much says it. This is w/regard to VxWorks; unfortunately, the documentation more or less says that it happens but not why or what purpose it serves.

Answer 1

It's been a few years since I had to deal with vxworks "munching", but what it does is create the C++ static constructor call table. It apparently isn't needed in the current (6.8+) versions that we're using now. What I recall was from 5.4, I think.