No. That's the kind of thing programmers build into software specifically so that you don't *have* to write documentation.

Let me put it another way: If the software tries to play an invalid file, then it is likely to crash. Preventing that from happening is called "bullet-proofing" in programmer-speak. The simplest way to bullet-proof an application against bad data is to skip over bad data.

You don't document bullet-proofing, you just *do* it. The better your application is bullet-proofed, the more reliable it is. You don't put into a manual "by the way, our application is bullet proofed against bad data". That'd be like a car owner's manual saying "the new 2008 Ford Compensator has an electrical system that no longer shorts out when you flip the switches in the wrong order".

I hope someone isn't trying to patent bullet-proofing. If they are, it's another illustration of everything that's wrong with software patents.