C # to write the control software running flash back, can't capture the error information-CodePudding

This is an occasional mistake, write software, every method can capture the error message, this time no error log, found to look into the system log, the error, supposedly memory problems, bosses, please answer.

CodePudding user response:

NTDLL. DLL modules???????

CodePudding user response:

The lack of underlying resources

CodePudding user response:

Met cannot recover crashed, that is, software of abnormal

You can before the collapse of the interceptor, and then use the minidump to catch a dump, and then use the dump analysis tool

AppDomain. CurrentDomain. UnhandledException +=
your processing method
Information before this method can intercept software crash, general here, of course, software has collapsed, already cannot be saved, can only be logged, grasp the dump for further analysis

CodePudding user response:

reference wanghui0380 reply: 3/f

collapsed, also is met cannot recover software exception

You can before the collapse of the interceptor, and then use the minidump to catch a dump, and then use the dump analysis tool

AppDomain. CurrentDomain. UnhandledException +=
your processing method
Information before this method can intercept software crash, general here, of course, software has collapsed, has been unable to save, can only be logged, dump for subsequent analysis of the

For c # programming, how can you prevent this kind of mistake? Is caused by memory leaks? If it is a general logic errors will be caught the error log

CodePudding user response:

reference 4 floor singularity code farmers reply:

Quote: refer to the third floor wanghui0380 response:
collapsed, also is met cannot recover software exception

You can before the collapse of the interceptor, and then use the minidump to catch a dump, and then use the dump analysis tool

AppDomain. CurrentDomain. UnhandledException +=
your processing method
Information before this method can intercept software crash, general here, of course, software has collapsed, has been unable to save, can only be logged, dump for subsequent analysis of the

For c # programming, how can you prevent this kind of mistake? Is caused by memory leaks? If it is the general logic errors are caught the error log

Not capture less than, but not capture,

UnhandledException exception handling is not, at the same time, is the current Domaind didn't handle all phases of exception, so the current domain out

I give you a real deal with the collapse of the way -- -- -- -- -- - is to tell you this collapse may not be the memory that you want to ah, leakage, maybe he's just a simple mistake

Real case:
A service breakdown, through UnhandledException Log, found that only a small abnormalities, and processes to monitor a directory file, in before the start of the third party software and deleted the file, so the openfile exception (although I code also caught the dump, but actually I didn't dump analysis, logging analysis alone can locate the)
Although this is only a very small anomaly, just because of this accident is no other place for processing, so collapsed, natural this exception I simply add a try when openfile did not collapse

CodePudding user response:

refer to the second floor xuzuning response:

the lack of underlying resources

reference 5 floor wanghui0380 reply:

Quote: refer to 4th floor singularity code farmers reply:

Quote: refer to the third floor wanghui0380 response:
collapsed, also is met cannot recover software exception

You can before the collapse of the interceptor, and then use the minidump to catch a dump, and then use the dump analysis tool

AppDomain. CurrentDomain. UnhandledException +=
your processing method
Information before this method can intercept software crash, general here, of course, software has collapsed, has been unable to save, can only be logged, dump for subsequent analysis of the

For c # programming, how can you prevent this kind of mistake? Is caused by memory leaks? If it is the general logic errors are caught the error log

Not capture less than, but not capture,

UnhandledException exception handling is not, at the same time, is the current Domaind didn't handle all phases of exception, so the current domain out

I give you a real deal with the collapse of the way -- -- -- -- -- - is to tell you this collapse may not be the memory that you want to ah, leakage, maybe he's just a simple mistake

Real case:
A service breakdown, through UnhandledException Log, found that only a small abnormalities, and processes to monitor a directory file, in before the start of the third party software and deleted the file, so the openfile exception (although I code also caught the dump, but actually I didn't dump analysis, logging analysis alone can locate the)
Although this is only a very small anomaly, just because of this accident is no other place for processing, so collapsed and natural this exception I simply add a try when openfile did not collapse

See, catch exceptions, abnormal analysis, can fundamentally solve the problem