> On Windows this > results in the famous general protection fault, on Unix it > results in the famous segmentation fault, and on z/OS it is > the famous SOC4. I wonder if there isn't a better way to > deal with this problem then just aborting the program. Users > find this problem really annoying.
This is programmer error -- the hardware is doing exactly what it should do, methinks. Correcting the developers usually helps, although that's much harder. I've yet to find a programming language or toolset that doesn't do exactly what the programmer tells it to do, even if it's stupid...8-) -- db
