\nIf you don’t want your program to display the standard\ncrash dialog,\nyou can disable it by setting the\nSEM_NOGPFAULTERRORBOX\nflag in the process error mode.\n<\/p>\n
\nThe simple-minded way is just to do\n<\/p>\n
\nSetErrorMode(SEM_NOGPFAULTERRORBOX);\n<\/pre>\n\nbut this overwrites the previous error mode rather than augmenting it.\nIn other words, you inadvertently turned off the other error modes!\n<\/p>\n
\nUnfortunately, there is no GetErrorMode function,\nso you have to do a double-shuffle.\n<\/p>\n
\nDWORD dwMode = SetErrorMode(SEM_NOGPFAULTERRORBOX);\nSetErrorMode(dwMode | SEM_NOGPFAULTERRORBOX);\n<\/pre>\n\nThis sets the new error mode (possibly disabling some other error\nmodes that had been set) and saves the previous mode. Then it\nsets the error mode the right way, adding the SEM_NOGPFAULTERRORBOX\nflag to the existing error modes.\n<\/p>\n
\nMerging with existing error modes is important.\nFor example, the previous error mode may have included\nSEM_NOALIGNMENTFAULTEXCEPT.\nIf you casually turned that off, then the program would not longer\nreceive automatic alignment fault fixups and will start crashing.\n<\/p>\n
\n(But if you read the documentation, you’ll see that\nSEM_NOALIGNMENTFAULTEXCEPT is special: The system won’t let you turn\nit off once it’s been turned on. Why? Because too many\npeople were already making this mistake<\/strong>.\nI remember before this special rule was introduced.\nPrograms were crashing left and right because they\ndidn’t do the double-set shuffle above; as a result, they\nstarted crashing on alignment faults.\nSo the special rule had to be added.\nWelcome to the world of compatibility, where it\nis the operating system’s duty to cover for other people’s mistakes.\nMind you, the design of\n\nthe SetErrorMode function<\/a> makes this mistake\na very easy one to commit.)\n<\/p>\n
\nNote that the error mode is a process-wide setting, not a per-thread\nsetting. This means that manipulating the process error mode is\nnot something you should do lightly, since it may have unintended\nconsequences for other threads (which you might not have control over).\nFor safety’s sake, a program should set its error mode when it starts\nup and not mess with it thereafter.\n<\/p>\n