I wrote a piece of code on Windows:
__try {
Foo_fun ();
{} __exception (EXCEPTION_EXECUTE_HANDLER)
//write some log...
}

Foo_fun () is a memory access code seams could occur, but in our test students found on a computer to generate a crash dump, the result is a collapse in the foo_fun ();
According to my understanding SEH should be able to capture all the hardware and software of the anomaly, it's a bit strange, don't know you know about this patch, welcome to discuss,

CodePudding user response:

__exception (EXCEPTION_EXECUTE_HANDLER)
Only capture this abnormal?

CodePudding user response:

No, this mean __try content as known exception handling,

CodePudding user response:

Test whether or not the students that computer configuration is low? You are using the system underlying debugging routines, if the response is likely to cause a system crash, overtime this routine should be very reliable,

CodePudding user response:

I looked at it and test the computer performance should not calculate is too low:
0:09 4 & gt; ! Cpuid
CP/M/S Manufacturer F MHz
0 6,78,3 GenuineIntel 2300
1 6,78,3 GenuineIntel 2300
2 6,78,3 GenuineIntel 2300
3 6,78,3 GenuineIntel. 2300

CodePudding user response:

Then how to see the fruits of the foo_fun processing, if the function also has the _try _except catch exceptions, exception may not pass to the higher level
Dump generated generally can copy to the original compiler generated directory, open the F5 debugging with VS, if generated from time to tome. PDB debug symbol file, you can see collapses and the call stack, it is easy to track the problem
Or installed on the machine can be easy to crash the remote debugger, so abnormal under open VS debug menu, under the remote debugging