Originally Posted by
Water pilot
I would put this in the software error category of failing to anticipate bad input, much like code that gets a packet that says that the remainder is 450 bytes long which then reads 450 bytes from the stream without verifying that there are actually that many bytes left in the stream. Anything that reads external data has to be able to anticipate bad input and do something appropriate in response. Just pretending that bad input is impossible or that somebody else will respond to it for you is not good design.
Stick to the pilot monkeying . . . this is a very intentional systems design issue, not a software implementation issue . . . you are so far out of your depth you don't even know what depth means . . .